Major REST book now available!

The book is called “RESTful Web Services” and O’Reilly, the publisher, finally released it. The authors, Leonard Richardson and Sam Ruby, guide you through a revealing journey inside the architecture of the Web. Using concrete examples, they help you to use HTTP, URIs and REST at their full potential.

A design process called Resource Oriented Architecture provides a pragmatic application of REST principles and best practices based on findings from the REST community. Also, this book is also the first one to significantly cover the Restlet framework, providing a good opportunity to compare it to other frameworks like Ruby on Rails and django.

For having had a chance to review it and to contribute the Restlet section (with the help of Dave Pawson), I think it is a must read for all REST and Restlet enthusiasts!

Update 1:

Update 2:

  • book review by Jon Udell (Microsoft)
  • book review by Henry Story (Sun) and relationship to RDF
  • book review by Paul Sandoz (Sun) and comments regarding content negotiation
  • book review by Jason Hudgins and comments regarding Restlet coverage

RESTful design of complex Web forms

In a previous post, I’ve introduced you to frevvo, a start-up that provides Web 2.0 visual forms, with a full WYSIWYG builder based on AJAX.

Recently, they have been playing with Restlet and implemented one of the REST design pattern (“View and Entity resources”) that was discussed by the Restlet community. It is a very compelling illustration that REST applications are perfectly capable of handling complex Web forms without compromising with the REST principles.

What is also cool is the fact that the Entity Resources can be either stored locally along with the View Resources (and accessed by a simple Restlet method call), or remotely and accessed by HTTP. This illustrates the power of uniform interfaces in REST/Restlet.


Congrats Ashish and Yuri, I look forward to reading the next blog entry in the series!

Update: two follow-up posts are available:

  1. Visual REST apps: Part 2 – documents
  2. Ajax+REST: the next killer app?