This month we are celebrating 5 years of Restlet open source development! Version 0.9 beta was the first public release made on November 2005.
Five years later, we still feel on the right path : leveraging REST to fully embrace the Web as the new development platform. We are still in the middle of the journey, with an exciting road ahead including the cloud computing, the rise of the mobile web and the upcoming HTML 5 standard.
Updated version tags
Today, we released the first milestone of version 2.1, our new “testing” version, as well as version 2.0.3 which is becoming our new “stable” version recommended for production. As a consequence, the 1.1 branch is still available for download here but has been archived.
We now encourage all developers to migrate to the latest greatest 2.0 branch for new deployments (see these instructions first). For new development projects, we encourage the usage of version 2.1 M1 which benefits from the stability of branch 2.0 for most parts, and adds new exciting features.
- All features deprecated in version 2.0 were completely removed, reducing the framework footprint
- Brand new internal HTTP connector (client and server) based on non-blocking NIO with initial performance close to extension connectors based on Apache HTTP Client 4.0 and Eclipse Jetty 7.1. This connector has already been significantly tested under load, with large entities and is fully configurable
- Removed the Grizzly and Netty extensions considered as experimental in version 2.0 to focus on our lighter NIO connector
- Representation class can now notify a listener of asynchronous content availability (ready to be read) or delivery (ready to be written). This has been tested to asynchronously receive CouchDB notifications
- Added support for GWT 2.1. Support for GWT 2.0 has been removed due to changes in GWT internal APIs, but is still supported in the 2.0 branch
Here is a summary of the planned features and tasks for version 2.1.0 which is scheduled for 2011 Q2:
- Finish the writing of the Restlet in Action book published by Manning
- Add a SIP connector extension based on the new NIO internal connector, providing a modern VoIP foundation for convergent web applications
- Enhance the ConverterService to support direct conversion between representations, from beans to representations and between beans
- Add a ConnegService to configure HTTP content negotiation and allow its customization. One use case is the negotiation between web representations of a resource based on agent type such as desktop browser and mobile browser
- Better integration with Eclipse ecosystem, with support for model-driven REST via extensions for EMF, ATL and Acceleo
- Migration from Tigris to JIRA Studio for SVN hosting, issue tracker, code search, code review, continuous build, etc.
- Alex Milowski
- Alexander Kampmann
- Alois Cochard
- Avi Flax
- Brian Cabana
- Bruno Harbulot
- Christophe Vanfleteren
- Daniel Zhelyazkov
- Darin Jackson
- David Fogel
- Doug Smalley
- Dustin Jenkins
- Evan Wang
- Fabian Mandelbaum
- Giovani Pieri
- Jean-Luc Geering
- John Logdson
- Laurent Rustuel
- M. Maksin
- Marc Portier
- Michael Terrington
- Nicolas Rinaudo
- Olivier Miel
- Olivier Monaco
- Rob Kooper
- Tal Liron
- Tim Peierls
- William Pietri
Thanks to all others who helped us in various ways for this first milestone, especially NetDev for funding a part of the new NIO connector and helping with testing and challenging use cases !