From: Boris Schäling (boris_at_[hidden])
Date: 2002-11-23 13:13:14
> -----Ursprüngliche Nachricht-----
> Von: boost-bounces_at_[hidden]
> [mailto:boost-bounces_at_[hidden]]Im Auftrag von Hugo Duncan
> Gesendet: Samstag, 23. November 2002 17:22
> An: boost_at_[hidden]
> Betreff: [boost] Sockets
> Sockets have come up from time to time on this list, without
> concrete results. I am no expert, but based on previous
> discussions, I have tried to start describing a design at:
> (I don't often write formal designs, so please excuse (or correct)
> misuse of terminology etc.)
> I propose working with a group of interested people to develop
> this design and put together some code.
> As my socket programming experience is limited to tcp/ip streams,
> I would also like to ask people to provide small test cases.
> In particular, examples of datagram usage, multicast,
> broadcast, and non-ip usage.
> Please feel free to edit the wiki pages with comments, etc.
I read your library requirements. I don't agree that a socket library should
wrap rather than invent. You write the "sockets interface is well known to
many programmers". If this is true noone will use a C++ library if it only
wraps but has no advantage over C functions. A C++ library should simplify
and wrap the complexity of the network. Eg. there is no need for Ip4Address
and Ip6Address classes if the library can find the protocol to be used by
looking at the given address - 0.0.0.0 for IP4 or 0::0 for IP6.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk