[JBoss JIRA] Commented: (NETTY-79) IdleChannelHandler

[Trustin Lee (JIRA)]

    [ https://jira.jboss.org/jira/browse/NETTY-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440677#action_12440677 ] 

Trustin Lee commented on NETTY-79:
----------------------------------

That's also an option I'm thinking about.  However, I'm somewhat concerned about the performance implications of running idleness detection in I/O thread.  Idleness detection is performed periodically, but it scans through the whole list of open channels which can be time consuming (i.e. O(N) operation.)

Therefore, at least I want to make it run in a separate thread with lower priority.  Does it make sense to you? :)

> 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.ALPHA2
>
>
> 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