Feature #251
Add ConnectionManagerEvent, separate from ConnectionEvent
| Status : | Closed | Start : | 10/29/2009 | |
| Priority : | Normal | Due date : | ||
| Assigned to : | colin moock | % Done : | 0% |
|
| Category : | Connection | |||
| Target version : | Reactor 1.0 Alpha 5 | |||
Description
In Reactor 1.0 Alpha 4 and earlier, all connection-related events were defined by ConnectionEvent, even though connection events were triggered by two different sources: the ConnectionManager and IConnection objects. ConnectionManager events should be separated so that they can be distinguished easily from individual IConnection events. Create a new class, ConnectionManagerEvent, to define the ConnectionManager's events. The ConnectionManagerEvent class's events indicate the success or failure of an entire list of connections, whereas ConnectionEvent indicates the success or failure of a single IConnection object only. ConnectionManagerEvent should also include a new event, SELECT_CONNECTION, which provides a means of detecting when the ConnectionManager has moved to a new connection in its connection list.
This change does not involve any changes to ReactorEvent.READY and ReactorEvent.CLOSE, so most existing developer applications will be unaffected, and will not require code modifications.
Also available in: Atom