Aaron W. LaFramboise wrote:
Perhaps a reason that noone has designed a really great sockets library yet is that there is little practical reason to, as BSD sockets is probably more portable (from a practical standpoint) than a Boost library will ever be, and libraries try to that "abstract" it have done nothing but get in the way.
Sockets themselves aren't that big a deal. The abstraction won't add a lot there, except for stuff like translating addresses from human-readable form to what is used by the sockets interface. The key functionality of a sockets library will be the dispatch mechanism. Something that streamlines how blocking/non-blocking mode interacts with select/poll/devpoll/windows events and a threaded vs reactive model will be highly valuable. Particularly if library allows the choices to be changed without affecting much/any of the code. -- Jonathan Biggar jon@levanta.com