Connectors

• Built-in HTTP client and server connectors were added right inside the Restlet Engine, with zero external dependency and a performance close to other connectors. This is the recommended choice during development phases. For production, we still recommend using our more robust Jetty connector.

• Powerful HTTP server connector based on Sun’s Grizzly NIO framework was added. It is the first to leverage the end-to-end NIO capacities of the Restlet API. For example, it allows direct transfer from files to sockets, reducing JVM memory usage and CPU consumption!

• Overall SSL support was greatly enhanced with access to new attributes for all HTTP connectors and with the addition of a new “com.noelios.restlet.ext.ssl” extension based on the jSSLutils library.

• New POP3 client connector based on JavaMail was added. It complements the existing SMTP client connector to allow Restlet applications to conveniently retrieve and send emails. The development was sponsored by RunMyProcess SAS.

• Partial GETs and PUTs are now supported by the FILE client connector. In addition with the new RangeService and Range classes, it now offers full and transparent support for HTTP “content ranges”, enabling important features such as partial retrievals and resumable uploads.

• The AsyncWeb HTTP server connector was removed. The AsyncWeb is currently being integrated with MINA, the NIO framework from Apache. We will introduce support for MINA in Restlet 1.2. But for Restlet 1.1, it didn't make sense to continue the support for AsyncWeb.

• The Jetty 5 HTTP server connector was removed and is replaced by the Jetty 6 connector which is now fully stable.