REST : Representational State Transfer

This word has been the buzz word in the internet for some time now and has really picked up recently. With the advent of Rails 2.0 and its support for REST, now the programming world is eying its implicabality in enterprise systems development. There is of course many speculatins ragarding the capabilities of REST and its limitations.Rails 2.0 has made it really easy to implement the fundamental principles of REST. In this tutorial we shall see the implementation senarious of REST architecture in RubyonRails and Jersey.

We shall also integrate the two applications and make a fresh newer application.consuming the services of both the jersey and rails.

Criterias for REST :

It has been well explained in the phd dessertion of Roy Fielding and wikipedia also has good reference to get ourself going. But we dont need to go on with these articles if we are working with Rails 2.0, because we can implement this architecture in REST in fly.

The core to REST is resource

Each resource must be identifiable by a unique URI

IT should adhere to the principles of statelessness, layering caching and client server.

Basically REST tells us to make use of those things which we have forgotten but is prevalent from early days of the internet. It basically makes use of all the four methods of HTTP along with PUT and DELETE which are as such not used much and are nt supported by the modern web browsers.