See my previous response. I think a well thought out boost scheduler/multiplexor module is needed. I would just focus on async network io in linux (preferably using epoll). Networking is one area where boost should probably have separate platform solutions so that best performance and elegance are not compromised. On top of that, having an acceptor and connector implementation with basic http examples would go a long way towards advancing in the right direction. If you plan to do this then I would gladly use it and provide feedback. I would wait first for more opinions. I am coming from the newbie boost user perspective that wants to build networking apps easily and doesn't need ACE. On 10 Aug 2005 19:26:15 +0200, Peter Simons <simons@cryp.to> wrote:
Jose writes:
Also worth checking the scheduler library in cryp.to [although it doesn't] seem to have active development.
I still maintain the library -- it's just that there isn't much to do anymore. To be considered as a Boost component, the Scheduler class would probably need to be made more generic. (Right now, the use of poll(2) is hard-coded, for example.) I'm open to making those changes, it's just that I didn't have the need to do it so far. If there is any interest, I'll gladly release the code under an all-permissive license instead of the GPL. I wanted to do that for a while anyway.
Peter
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost