My vote, YES.
charlie....
Jeanfrancois Arcand wrote:
> Hi,
>
> right now it is possible to have a single Controller that handle
> multiple SelectorHandler. By default, the SelectorHandler uses the
> same Pipeline (Thread Pool). I would like to add a new interface to
> the SelectorHandler interface that does:
>
> /**
> * Return the Pipeline used to execute this SelectorHandler's
> * SelectionKey ops
> * @return The pipeline to use, or null if the Controller's Pipeline
> * should be used.
> */
> public Pipeline pipeline();
>
> This way people that wants to have multiple pipeline (or pipeline per
> SelectorHandler) will have a way to make it work. Note that the
> default behavior will be preserved, which consist of using a single
> Pipeline for all SelectorHandler. Also I will make sure this interface
> is properly documented as having multiple pipeline might significantly
> reduce performance (at least for the http path, it gives disastrous
> results).
>
> Any thought?
>
> Thanks
>
> -- Jeanfrancosi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
--
Charlie Hunt
Java Performance Engineer
630.285.7708 x47708 (Internal)
<http://java.sun.com/docs/performance/>