You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/07/13 05:06:09 UTC
[jira] Created: (DIRMINA-400) Selective event processing in
ExecutorFilter
Selective event processing in ExecutorFilter
--------------------------------------------
Key: DIRMINA-400
URL: https://issues.apache.org/jira/browse/DIRMINA-400
Project: MINA
Issue Type: New Feature
Components: Filter
Reporter: Trustin Lee
Assignee: Trustin Lee
Fix For: 2.0.0-M1
Previous implementation of ExecutorFilter forwarded only sessionOpened, sessionIdle, sessionClosed, messageReceived and messageSent events to the executor. It often becomes a cause of resource contention for other I/O events such as filterWrite.
If we can provide a set of event types that has to be forwarded to the executor, we will be able to apply more sophisticated thread model. The following is a typical usage example:
chain.addLast("executor1", new ExecutorFilter()); // Default behavior of ExecutorFilter will be retained.
chain.addLast("codec", new ProtocolCodecFilter(...));
chain.addLast("logger", new LoggingFilter());
chain.addLast("executor2", new ExecutorFilter(IoEventType.WRITE, IoEventType.CLOSE));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRMINA-400) Selective event processing in
ExecutorFilter
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRMINA-400.
-------------------------------------
> Selective event processing in ExecutorFilter
> --------------------------------------------
>
> Key: DIRMINA-400
> URL: https://issues.apache.org/jira/browse/DIRMINA-400
> Project: MINA
> Issue Type: New Feature
> Components: Filter
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Fix For: 2.0.0-M1
>
>
> Previous implementation of ExecutorFilter forwarded only sessionOpened, sessionIdle, sessionClosed, messageReceived and messageSent events to the executor. It often becomes a cause of resource contention for other I/O events such as filterWrite.
> If we can provide a set of event types that has to be forwarded to the executor, we will be able to apply more sophisticated thread model. The following is a typical usage example:
> chain.addLast("executor1", new ExecutorFilter()); // Default behavior of ExecutorFilter will be retained.
> chain.addLast("codec", new ProtocolCodecFilter(...));
> chain.addLast("logger", new LoggingFilter());
> chain.addLast("executor2", new ExecutorFilter(IoEventType.WRITE, IoEventType.CLOSE));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRMINA-400) Selective event processing in
ExecutorFilter
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trustin Lee resolved DIRMINA-400.
---------------------------------
Resolution: Fixed
Done. Please review.
> Selective event processing in ExecutorFilter
> --------------------------------------------
>
> Key: DIRMINA-400
> URL: https://issues.apache.org/jira/browse/DIRMINA-400
> Project: MINA
> Issue Type: New Feature
> Components: Filter
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Fix For: 2.0.0-M1
>
>
> Previous implementation of ExecutorFilter forwarded only sessionOpened, sessionIdle, sessionClosed, messageReceived and messageSent events to the executor. It often becomes a cause of resource contention for other I/O events such as filterWrite.
> If we can provide a set of event types that has to be forwarded to the executor, we will be able to apply more sophisticated thread model. The following is a typical usage example:
> chain.addLast("executor1", new ExecutorFilter()); // Default behavior of ExecutorFilter will be retained.
> chain.addLast("codec", new ProtocolCodecFilter(...));
> chain.addLast("logger", new LoggingFilter());
> chain.addLast("executor2", new ExecutorFilter(IoEventType.WRITE, IoEventType.CLOSE));
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.