> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Darryl Green
> Sent: Thursday, November 28, 2002 2:24 AM
> To: Boost mailing list
> Subject: RE: [boost] Socket Multiplexing
>
> [...]
> > observer is not the problem b
> -Original Message-
> From: Boris Schäling [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 28 November 2002 5:14 AM
[snip]
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
> > Sent: Wednesday, November 27, 2002 1:41 PM
[s
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
> Sent: Wednesday, November 27, 2002 1:41 PM
> To: Boost mailing list
> Subject: RE: [boost] Socket Multiplexing
>
>
> On Tue, 2002-11-26 at
On Tue, 2002-11-26 at 20:55, Boris Schäling wrote:
> > * should not require virtual base class interface
>
> What does this mean? No polymorphism?!
No, it just means templates (compile time polymorphism).
Higher levels can add virtual functions but we shouldn't need them in
the lower layers. Ev
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Darryl Green
> Sent: Wednesday, November 27, 2002 1:27 AM
> To: Boost mailing list
> Subject: RE: [boost] Socket Multiplexing
>
>
>
>
> > From: Boris Schäling [
> From: Boris Schäling [mailto:[EMAIL PROTECTED]]
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Hugo Duncan
> > [...]
> > * a multiplexing library should cope with:
> > files,
>
> How should files be supported by a multiplexing library? In Unix/Linux
> file
> access ne
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Hugo Duncan
> Sent: Monday, November 25, 2002 11:38 PM
> To: [EMAIL PROTECTED]
> Subject: [boost] Socket Multiplexing
>
>
> Boris and Hamish have presented examples using objects that
> provide fat int
Hugo Duncan wrote:
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.
ACE (I think) uses enums to register i
