Re: [boost] Re: Sockets library requirements

From: Timothy M. Shead (tshead_at_[hidden])
Date: 2002-02-24 19:54:41

On Sun, 2002-02-24 at 16:03, davlet_panech wrote:
> --- In boost_at_y..., "Vladimir Ciobanu" <psycho_at_t...> wrote:
> >     I've talked about this with serveral people and they pointed 
> out that
> > it doesn't make sense to derive a socket from any standard stream. 
> The
> > reason is that there are some functions which simply don't make 
> sense
> > for a socket stream. Example:
> > 
> > seek*( )
> > 
> 
> Could you give more examples? The thing is, seek*() is a noop for 
> standard streams (stdin, stdout) also, so I don't see this as a big 
> problem.

As you say, the seek issue is not a big deal, and there's no compelling
reason *not* to heave stream interfaces for a socket; that said, you may
find (as I am finding right now) that framing, blocking, and
error-handling issues tend to make the stream inserter/extractor
interface less useful than it might seem.

Tim Shead