Re: Sockets library requirements

From: davlet_panech (davlet_panech_at_[hidden])
Date: 2002-02-24 20:08:53

--- In boost_at_y..., "Timothy M. Shead" <tshead_at_k...> wrote:
> On Sun, 2002-02-24 at 16:03, davlet_panech wrote:
> > 
> > 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.

Perhaps; although framing is not an issue for stream-based protocols. 
Blocking doesn't seem like a big issue for a stream also -- after all 
file streams are blocking, even though the underlying OS frequently 
supports non-blocking file operations. I think I agree that error 
handling might be problematic, though.

D.P.

> 
> Tim Shead