Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Abandoned
-
2.0.0-M3
-
None
-
None
Description
The way we are selecting a message handler in the DemuxingIoHandler is far from being optimal. The problem is that we are registering a handler without checking its inheritence scheme, but we do so when receiving a message.
It would be much more efficient to do the inheritence discovering while registering a handler, avoiding such a discovery when receiving a message.
There is only one tricky issue we have to take care of : as we can associate a handler with one of it's inherited class or implemented interface, if there is another handler associated with those classes/interfaces added later, this should override the default association. So we must flag the automatically added handlers in order to be able to replace them if needed.