From: Boris Schäling (boris_at_[hidden])
Date: 2002-11-26 15:55:44
> -----Original Message-----
> From: boost-bounces_at_[hidden]
> [mailto:boost-bounces_at_[hidden]]On Behalf Of Hugo Duncan
> Sent: Monday, November 25, 2002 11:38 PM
> To: boost_at_[hidden]
> Subject: [boost] Socket Multiplexing
> Boris and Hamish have presented examples using objects that
> provide fat interfaces for event notification. By this I mean they use
> seperate onEvent() handlers for each type of event as member functions
> of an event sink or observer class.
> * a multiplexing library should cope with:
How should files be supported by a multiplexing library? In Unix/Linux file
access never blocks? The man page of select() says: "File descriptors
associated with regular files always select true for ready to read, ready to
write, and error conditions."
> * should not require virtual base class interface
What does this mean? No polymorphism?!
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk