[JBoss JIRA] Closed: (NETTY-194) Allow different key other than Channel in OrderedMemoryAwareThreadPoolExecutor

[Trustin Lee (JIRA)]

     [ https://jira.jboss.org/jira/browse/NETTY-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee closed NETTY-194.
-----------------------------

    Resolution: Done


Done.  A user now can specify a different key.  How-to is documented in Javadoc of OMATPE.

> Allow different key other than Channel in OrderedMemoryAwareThreadPoolExecutor
> ------------------------------------------------------------------------------
>
>                 Key: NETTY-194
>                 URL: https://jira.jboss.org/jira/browse/NETTY-194
>             Project: Netty
>          Issue Type: Feature Request
>          Components: Handler
>            Reporter: Trustin Lee
>            Assignee: Trustin Lee
>             Fix For: 3.1.0.GA
>
>
> OMATPE maintains the order of event handler execution based on the Channel that the ChannelEvent belongs to, which means events for the same Channel cannot be handled  concurrently.  However, in a certain case, a user will want the events to be handled concurrently for the same Channel but not for the same business logic dependent key.  To support the easy implementation of such a ThreadPoolExecutor implementation, we need to make OMATPE extensible.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira