From: Boris Schäling (boris_at_[hidden])
Date: 2002-11-27 03:39:39
> -----Original Message-----
> From: boost-bounces_at_[hidden]
> [mailto:boost-bounces_at_[hidden]]On Behalf Of Darryl Green
> Sent: Wednesday, November 27, 2002 1:47 AM
> To: Boost mailing list
> Subject: RE: [boost] Re: AW: Re: AW: Sockets
> > Good point. There is currently no UDP support in my library.
> Maybe traits
> > could be used to tell the stream to discard data that couldn't
> be written
> > immediately? I am not sure if anything else had to be changed for UDP?
> I really think a lower level/more flexible interface than the one
> you propose needs to be provided if the concept is generalised
> beyond common "socket" types (which is necessary, to me at least,
> that's why we have written one - unfortunately I can't provide
> source). Even with the more common socket types, there are some
> interesting usages to consider as Hamish suggests. Out lib uses a
Okay, no problem for me. Then we should start and complete a library design?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk