Hello again.

Ok, now I'm sure Boost.Fiber is the only (simply) way I have to solve my problem.

The project on which I'm working, requires a TCP session per client. Between the client and the server, it is possible that at some point in time, the client and the server will have to manage different contexts of conversations using the same TCP Session. 

I simply don't know how to do this in the old fashion way. Documentation regarding coroutines is scarce and the examples are too simplistic. What I know is that the Fiber Documentation provided by Oliver states that Boost.Coroutine does not provide a way to synchronize different coroutines execution.

Anyway, it seems that I definitely have to use Oliver's Fiber lib. 
So now my problem is, how do I build this lib? How can I compile it and link it to the boost libs already installed in my computer? The readme.md file says to look at the docs in https://svn.boost.org/trac/boost/wiki/TryModBoost but that left me kinda lost...

Thanks for any help!


On 20 January 2014 17:33, Lars Viklund <zao@acc.umu.se> wrote:
On Mon, Jan 20, 2014 at 04:48:45PM +0000, Carlos Ferreira wrote:
> Is it possible to say when will the Fiber lib be givin the "ok!" to be used
> in a production environment?

When the review manager has collected all the feedback and reviews, and
made an informed decision on its acceptance, conditional acceptance or
rejection from Boost.

As for "production environment", the inclusion into Boost doesn't really
guarantee any of that sort. It's up to you to judge if the problems
raised during the review process are blocking enough for you to trust it
in production.

Some libraries that are rejected are still very usable in their proposed
non-accepted form, while some libraries are accepted even if they are
brittle and in need of some serious work to be "production-grade".

In the end, it's a judgement you have to make off the reviews, the
review-manager's summary and all the things that crop up once people
start to try to use the library.

As for absolute timeframes between reviews and resolution, anything from
a few days from the review deadline to several weeks afterwards based on
a sampling of earlier review results. This assumedly varies a lot based
on the issues raised during review and the spread of reviews.

--
Lars Viklund | zao@acc.umu.se
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users



--

Carlos Miguel Ferreira
Researcher at Telecommunications Institute
Aveiro - Portugal
Work E-mail - cmf@av.it.pt
Skype & GTalk -> carlosmf.pt@gmail.com
LinkedIn -> http://www.linkedin.com/in/carlosmferreira