dev@grizzly.java.net

Re: handling SelectionKey.OP_ACCEPT without invoking a chain of filters added in Transport.

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Thu, 17 Dec 2009 10:58:52 +0100

Hi Ming Qin,

please try
filterChain.setInterested(IOEvent.SERVER_ACCEPT, false);

WBR,
Alexey.

On Dec 17, 2009, at 8:37 , ming qin wrote:

> For Grizzly 2.0.0-M3, after SelectionKey.OP_ACCEPT ‘s firing
> IOEvent.SERVER_ACCEPT , can SelectorRunner not to invoke a chain of
> filters being defined in Transport?
>
> Transport is added with a series filters as a chain of filters.
> when client requests a connection with server, the server’s
> SelectorRunner invokes fire(key, IOEvent.SERVER_ACCEPT), as well as
> those filters being added in Transport are invoked.
>
> By avoiding invoking those filters in transport for
> SelectionKey.OP_ACCEPT,
> SelectionKey.OP_ACCEPT related ready-operation should run on a fast
> track, if there are no datai is supposed to pass into those filters.
>
>
>
> Ming Qin
> Cell Phone 858-353-2839
>
>