Hi Brandon, > 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.
If you can cast the request inputstream to a Jetty class that gives you access to the underlying NIO channel, that might work. I haven't found the JettyInputStream class in the API or another way to access to the channel. Any clue? Thanks, Jerome
