Hi Brandon, I have done some research in the past in this area. See this report: http://restlet.tigris.org/issues/show_bug.cgi?id=143
I have just changed the milestone to 1.1 and added a comment mentionning your proposition. Feel free to add more comments while you experiment. BTW, I'm not convinced yet of the need for continuations or COMET-style communications and on the compliance with the HTTP standard. It seems that requiring your AJAX client to poll regularly the server, using properly configured caching metadata (like "last-modified" and "if-modified-since" headers) could be a better (more scalable) approach. What are the opinions on this? Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Brandon Lonac > Envoyé : mardi 30 janvier 2007 21:56 > À : discuss@restlet.tigris.org > Objet : Restlet and Jetty Continuations. > > For the project that I am using Restlet on, we are using a > pipeline approach to > process requests. This gives us the ability to really tune > persistence and > business logic pools separately. The NIO support in Restlet > is great, but we > want to use the Jetty Continuations as well. I have been > doing some digging as > to where I can put Continuations in. I am running Restlet in > the Jetty servlet > container not standalone. > > It looks like the either subclassing > com.noelios.restlet.ext.servlet.ServerServlet or > com.noelios.restlet.http.HttpServerHelper to start the > Continuation in the > .handle methods is the place to do the work. > > I'm also wondering if anyone has integrated Restlet w/ > Continuations yet as well? > > Thanks. > -Brandon
