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 interest in read/write, close, exception
activity on a resource.

boost::signal library seems a natural candidate for this. It has all the features you required, but without any complexities from using Observer pattern and similar (I apologize if I misunderstood your post - you do want a signal handling for socket events, right?)

Miro


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


Reply via email to