Hi, On Wed, 2005-04-13 at 11:24 +0200, Douglas Gregor wrote:

On Apr 13, 2005, at 10:49 AM, Boris wrote:

Here's the problem: we've been discussing and working on a sockets library for *years*. People have come, started working on it, and left before anything ever came up for review. It's getting to the point where it's become embarrassing to Boost that we *don't* have a sockets library yet.

Here's more motivation: the C++ committee is planning to finish the next revision of the C++ standard in the next few years, and I stress *few*. Boost has been a wonderful source of libraries for the C++ committee, and C++ would be greatly improved if the next version of the standard library contained a sockets library... this library could be that library, but we have to finish it, review it, and be sure it's right. We can't review what doesn't come up for review. "Finished" is more important than "complete".

I won't make any promises ( i did that before and was not able to keep them ) but I'm hoping to publish my socket lib ( layer 1) in the next few weeks. The design is complete ( I hope ) after many revisions and I am currently implementing it again. Basic concepts supported are: address socket select fd_set socket_options Protocol support is for IPv4 and IPv6 with unicast, broadcast, and multicast. additionally, I have support for routing, raw, and data link layer sockets. Initial implementation will be for gcc and Linux only and once I have had a preliminary review I'll add Intel on Linux , and GCC on Windows Impl. /ikh