Jerome Louvel <contact <at> noelios.com> writes:
> That should be all you need it in theory. In practice, you will be limited > by the fact that Jetty's NIO support is limited to the front-end of the > connector (dealing with the socket and the thread pool). The back-end part > is based on the Servlet API which forces you to see things as BIO streams. > > IMO, we'll only see the full benefit of NIO with Restlets when a dedicated > connector, based on MINA or Grizzly (to facilitate the NIO processing). MINA > is still digesting the merging with AsyncWeb but the Grizzly project > recently became a top-level project (https://grizzly.dev.java.net/) and we > might see some good progress on the Grizzly connector front soon. You can > contribute to this new connector here: > http://restlet.tigris.org/issues/show_bug.cgi?id=16 > > Best regards, > Jerome > Ah, ok that all makes sense. I did see that in the latest jetty release of 6.1.1, they officially added the support to use grizzly as the front end connector. So even if i fronted jetty w/ grizzly, I will be stuck to getting the incoming request as a BIO stream. When I was debugging I saw that the underlying JettyInputStream was a NIO channel. So this is still being limited by the servlet api in the request hand off? Sorry all my questions, I have been just recently digging deep into the servlet spec.
