Hi Bruce, If you use the Jetty connector JARs instead of deploying a WAR, you will NOT go through their Servlet container layer.
I know this sounds strange because there is a dependency on the Servlet API JAR, but for having written most of this code and having looked closely at Jetty's code, it really uses a shortcut inside Jetty at the lowest level. For sample code, add the required Jetty JARs to your classpath (com.noelios.restlet.ext.jetty_6.1.jar, etc.) and see the tutorial part 5 to create a standalone Component: http://www.restlet.org/documentation/1.1/tutorial#part05 Best regards, Jerome -----Message d'origine----- De : news [mailto:[EMAIL PROTECTED] De la part de Bruce Lee Envoye : mardi 24 juin 2008 21:51 A : [email protected] Objet : Re: Using Grizzly adapter with Restlet Jerome Louvel <contact <at> noelios.com> writes: > > Also, the way the Jetty connector for Restlet works doesn't require the > costly Servlet container layer, it's using a lower level Jetty API. So > performance are very good and could be compared to those of the Grizzly > connector for Restlet. Hi Jerome, I was able to port my application directly to use the Jetty http connector by following http://www.restlet.org/documentation/1.1/connectors. However, such approach utilizes Jetty's Servlet container layer, which we would like to avoid. Can you provide a simple example of using Jetty connector for Restlet directly without the Servlet container? Regards,
