Feature #674

Updated by J. Moringen almost 12 years ago

In order to deal with situations where client code waits in callbacks, e.g., in a blocking call for getting the next event and an exception occurs in the ReceiverTask of the framework we need a mechanism to communicate the exceptional status to the client. Only when the client is explicitly informed, it will be possible for him to react accordingly and shutdown its listener threads.

The communication from ReceiverTask to a client via the EventHandler (which is there the router object) may be a first test case.

See [[ErrorHandling#Implementation-Concept]].

Back