Hi Greg,
We plan on exposing some of the NIO2 APIs and possibly even utilize
it. I have been spending some time on NIO2 for the async io as well as
the file system API to come up with a proposal. At this time I don't
have a concrete proposal but should have something soon hopefully as a
first draft.
- Rajiv
On 06/30/2011 06:49 PM, Greg Wilkins wrote:
> Is there a rough proposal yet of what aspects of NIO.2 that might be
> exposed in servlet 3.1?
>
> We've had a bit of a look at NIO.2 to consider if we can rework much
> of the jetty IO layer to use it, but have concluded that while the API
> does give very simple clean async code, it is not really suitable for
> large scale deployments as it has a number of scalability issues (eg.
> must allocated read buffers for idle connections and some
> inefficiencies with double dispatch to thread pools for each read).
> Thus we are unlikely to adopt NIO.2 as the core IO mechanism.
> However, we should be able to expose NIO.2 interfaces over NIO.1 IO.
> So any use-cases, examples or thought bubbles about NIO.2 usage plans
> would be helpful to guide NIO.2 adoption plans.
>
> cheers