On Feb 5, 2008 3:38 AM, Jerome Louvel <[EMAIL PROTECTED]> wrote:

> However, they can't leverage NIO from the socket to the Servlet as the
> Servlet API has no provision for NIO as explained above. This is where the
> Restlet API makes the difference, by introducing the Representation class
> based on the idea of contentlets suggested by Greg Wilkins (Jetty).
>

I hate to sound like a broken record, but the Restlet Request and Response
classes are not thread-safe, so Restlet cannot yet take *full* advantage of
NIO to break out of the thread-per-request paradigm. (There is movement on
this front, however, as Rob Heittman pointed out earlier in this thread.)

--tim

Reply via email to