Re: [boost] surveying async network io libraries

From: Jose (jmalv04_at_[hidden])
Date: 2005-08-10 16:05:42

Thank you for clarifying. 

If the goal for your library is to improve it and get a lot of users
then I think the http examples are needed, even before adding more
features. Probably  80% of networking code today has http in it.

If the goal is not that one, then it's probably a traditional
corporate project driven by other goals. I just want to know the goals
before investing lots of time using your library or providing feedback

It's a pity that there is not a widely used c++ net library and ACE is
not a practical  solution for many of the boost users. I just hope
that one of these libraries here or a combination of all of them will
get some traction and we can all benefit. This obviously requires some
additional effort from the main library authors but responding to
potential users makes the library move forward.

Unfortunately writing good examples is not something that a new
library user like me can do easily.

On 8/10/05, Christopher Kohlhoff <chris_at_[hidden]> wrote:
> Hi Jose,
> 
> I have a couple of comments on asio's cons, as you listed them...
> 
> --- Jose <jmalv04_at_[hidden]> wrote:
> > asio (asio.sf.net)
> > ===
> >
> > pros
> > - async network io ready (linux epoll as of 0.31)
> >
> > cons
> > - basic real world code examples (but no http examples)
> 
> I can say that asio has been successfully used to develop HTTP servers
> and clients (as well as many other protocol implementations such as
> XMPP and SOCKS). Of course, that doesn't really help if you are looking
> for an example! I'd love to add to the examples included with the
> library, but unfortunately paid work takes priority.
> 
> > - does not use boost threads
> 
> asio does not use boost threads for any internally created threads, and
> includes its own thread wrapper class, because my customers required a
> header-file-only library.
> 
> However, you are free (and I would encourage you) to use boost threads
> to invoke the demuxer's run function from a thread, e.g.
> 
>  asio::demuxer d;
>  boost::thread th(boost::bind(&asio::demuxer::run, &d));
>  ...
>  th.join();
> 
> Furthermore, the Linux/UNIX implementation of asio does not create
> *any* internal threads, so the only threads in your process would be
> ones you create using boost (or whatever other method you prefer).
> 
> Cheers,
> Chris
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>