Hi Tim, Very good point. Now that I've read the "Java Concurrency in Practice" book (excellent BTW!), I fully realize how this point is crucial.
Let's tackle it with the on-going Grizzly HTTP and GWT efforts. I've added your comment here: "Complete Grizzly connector" http://restlet.tigris.org/issues/show_bug.cgi?id=341 Best regards, Jerome > -----Message d'origine----- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la > part de Tim Peierls > Envoyé : mardi 5 février 2008 13:51 > À : [email protected] > Objet : Re: Evaluating Restlet > > 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 > >
