I like this idea. Because earlier, if wanted to have SelectionKeyHandler
without keeping alive, we had to subclass DefaultSelectionKeyHandler and
override expire method.
So, I'm +1 :)
Thanks.
WBR,
Alexey.
charlie hunt wrote:
> Is there an implementation of a SelectionKeyHandler without keep alive ?
>
> If not, would it make sense to insert into the hierarchy between the
> SelectionKeyHandler interface and DefaultSelectionKeyHandler a
> SelectionKeyHandler that does not implement keep alive?
>
> Today we have:
>
> SelectionKeyHandler (interface)
> |
> DefaultSelectionKeyHandler (implements SelectionKeyHandler and
> integrates keep alive)
>
> How about doing this?
>
> SelectionKeyHandler (interface)
> |
> BaseSelectionKeyHandler (implements SelectionKeyHandler,
> but no keep alive)
> |
> DefaultSelectionKeyHandler (extends BaseSelectionKeyHandler
> with keep alive support)
>
> This would allow one to easily configure a Grizzly transport where
> keep alive is not needed / required.
>
> Or, maybe I missed such an existing class already in the Grizzly?
>
> What do you think?
>
> charlie ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>