BoostSocket/Level1Design

boost::socket Level 1

Aim to provide a very light weight wrapper to the platform socket API, giving platform independence for higher levels. No attempt at this level to remove proconditions from platform API.

The design works with concepts (more or less) so that we can provide address and protocol indpendence without virtual function overhead.

If runtime polymorphic protocol/address types are required, they can always model the concepts described here, and use this layer as is.

• Platform specific type wrapping - type used by platform to represent a socket
• SocketError concepts- return values, and error handling
• TimeValue concepts- times for timeouts, etc
• IoctlOption Concept - ioctl handling
• SocketOption Concept - socket option handling
• Address Concept
• Address Info Concept - obtain info on addresses (ala getaddrinfo)
• Interface Info Concept - obtain interface information (address, netmask, etc)
• ProtocolConcept
• SocketSet Concept
• SocketBase Concept
• AsynchSocketBase Concept
• AsynchProactor Concept - does this belong on this level or Level2 or Multiplexing
• SocketReactor Concept - does this belong on this level or Level2 or Multiplexing