From: Boris Schäling (boris_at_[hidden])
Date: 2002-02-23 18:50:40
> -----Ursprüngliche Nachricht-----
> Von: jelco78 [mailto:marcojez_at_[hidden]]
> Gesendet: Samstag, 23. Februar 2002 16:53
> An: boost_at_[hidden]
> Betreff: [boost] Sockets library requirements
> Hello everyone, this is my first post in this group.
> Browsing the mailing list archive I found the "Sockets Library
> Requirements" document, which defines the guidelines for writing a
> socket library, so I thought that if such a library has not been
> written yet, I could help its development someway.
I didn't know of the guidelines until I read your mail. :)
I like requirement No. 1 "It must be easy to write safe network programs".
Problem with lots of socket libraries is that the user must know a lot of
how networks work.
> Some months ago, I wrote a socket library for my own use, and now I
> can see it meets almost all of the requirements listed in the
> guidelines document.
If you like to send me your socket library I'll have a look at it.
> Only one thing: I can't understand the purpose of "Layer 2" in the
> proposed design. The library I wrote was composed of only 2 layers:
> a first, low-level, portable wrapper class set for sockets and
> addresses (which show a 100% ISO C++ interface, and a portable
> implementation), and then an higher-level stream interface (based on
> a std::basic_streambuf derivation).
> So, what is the purpose and structure of "Layer 2" as described in
> the guidelines?
Don't know. It's probably only an example - at least this says the line
above the paragraph.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk