|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
29/Nov/05 11:52 PM
|
|
Jose Alberto Fernandez wrote:
Another matter around Demux, is that currently it only looks at super-interfaces if a direct match is not found,
But it does not look at super-classes. This is annoying when you have protocols that extend all messages from some particular superclass and you want to be able to treat groups of messages the same way (like ignoring them).
Also, it may be interesting to see if there is a good way to cache the resolution of super-interfaces and super-classes in order to make such code more efficient. You will just need to make sure that the cache is flushed when MessageHandlers are added or removed.
|
|
Description
|
Jose Alberto Fernandez wrote:
Another matter around Demux, is that currently it only looks at super-interfaces if a direct match is not found,
But it does not look at super-classes. This is annoying when you have protocols that extend all messages from some particular superclass and you want to be able to treat groups of messages the same way (like ignoring them).
Also, it may be interesting to see if there is a good way to cache the resolution of super-interfaces and super-classes in order to make such code more efficient. You will just need to make sure that the cache is flushed when MessageHandlers are added or removed.
|
Show » |
| No work has yet been logged on this issue.
|
|
Improvement
Closed
Minor
DemuxingIoHandler should look up super classes, too, and cache the lookup results.
