> > Hi Bruce, > > Currently, the Grizzly connector is not ready for production. There are a > couple of outstanding bugs that we need to fix. We'd like to run some > benchmarks as well before final 1.1 release. > > However, even if 1.1 release should be ready for production, it would still > be marked as "testing" in our download page: > http://www.restlet.org/downloads/ > > It's only a couple of months after, when we release 1.2 M1, that 1.1 release > will become the "stable" official release instead of 1.0. We try to follow a > release cycle similar to Debian. > > Now, if stability matters the most, I would recommend using the Jetty > connector instead, which we have since Restlet 1.0. > > Regarding connectors configuration, check this page: > http://www.restlet.org/documentation/1.1/connectors > > Best regards, > Jerome >
Hi Jerome, Thanks for the detailed response. The main reason we want to use Grizzly directly is because we simply want a high performance http/https connector without any web server capabilities. Embedding Jetty seems like a reasonable approach but we are concerning about the extra processing overhead. Also since Jetty can use Grizzly connector as well, would you recommend using the Jetty extension with Grizzly connector instead of their default connector? P.S. Is there an existing example of setting up HTTPS using Grizzly connector? Regards,
