|
Home > Archive > Apache Directory Project > November 2005 > [jira] Assigned: (DIRMINA-118) DemuxingIoHandler should look up super classes, too, an
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[jira] Assigned: (DIRMINA-118) DemuxingIoHandler should look up super classes, too, an
|
|
| Niklas Therning (JIRA) 2005-11-29, 7:45 am |
| [ http://issues.apache.org/jira/brows...NA-118?page=all ]
Niklas Therning reassigned DIRMINA-118:
---------------------------------------
Assign To: Niklas Therning (was: Trustin Lee)
> DemuxingIoHandler should look up super classes, too, and cache the lookup results.
> ----------------------------------------------------------------------------------
>
> Key: DIRMINA-118
> URL: http://issues.apache.org/jira/browse/DIRMINA-118
> Project: Directory MINA
> Type: Improvement
> Versions: 0.8
> Reporter: Trustin Lee
> Assignee: Niklas Therning
> Priority: Minor
> Fix For: 0.9
>
> 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 o
r removed.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
|
|
|