[JBoss JIRA] Commented: (NETTY-79) IdleChannelHandler
Christian Migowski (JIRA)
jira-events at lists.jboss.org
Thu Dec 4 02:46:36 EST 2008
[ https://jira.jboss.org/jira/browse/NETTY-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12441058#action_12441058 ]
Christian Migowski commented on NETTY-79:
-----------------------------------------
If the event is fired close to the time it was configured it doesn't matter how it is done internally (from my API-users point of view).
The idea to do it in a seperate thread seems reasonable to me (although I didn't know it is time-consuming; but then I am not very familiar with the Java networking internals).
> IdleChannelHandler
> ------------------
>
> Key: NETTY-79
> URL: https://jira.jboss.org/jira/browse/NETTY-79
> Project: Netty
> Issue Type: Feature Request
> Components: Handler
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Fix For: 3.1.0.ALPHA3
>
>
> Netty core doesn't detect an idle channel at all. There should be a ChannelHandler which triggers some action when a connection becomes idle. For example, a connection which didn't send a certain message for a certain amount of time could be closed automatically. To fulfill this requirement,
> 1) A user should be able to define what an 'idle' channel is. (sensible default would be 'no communication for 10 seconds' for example)
> 2) A user should be able to define what action should be performed when a channel becomes idle. (sensible default would be disconnection for example)
> 3) A user should be able to add multiple instances of this handler so that one can enforce multiple rules.
--
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
More information about the netty-dev
mailing list