[boost] Re: async socket i/o [long]

From: Michel André (michel.andre_at_[hidden])
Date: 2005-04-13 15:56:23

Boris wrote:
> read and write operations are still missing in this class hierarchy which I 
> agree is not helpful. :) Actually I didn't plan to add them to class socket 
> but only to class datagram, passive and connector. Maybe it makes sense to 
> create an iosocket class which provides read and write operations and 
> inherit datagram, passive and connector from it. In your design you don't 
> inherit connector from io_stream for the only reason because you don't and 
> can't do so with acceptor?

No it is to completely decouple connection establishment both on the 
server and the client from the actual stream or connection interface. 
The force behind this is that often the configuration of protocols and 
adresses is done quite far away from the stream and actual protocol 
needed. Usually its set up during init of server from a config file. The 
configurator could then set up a couple of acceptors and or connectors 
and send them away to the logic of the server that don't need to care 
about addresses or protocols and they act as factories for new streams.

/Michel