dev@grizzly.java.net

[Proposal - vote] Adding Pipeline interface to the SelectorHandler

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Mon, 18 Jun 2007 15:38:49 -0400

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