to homepage
 Weekly emails: how to  


> glossary > REST


(REpresentational State Transfer) A model for web services based solely on HTTP. REST takes the view that the Web already has everything necessary for web services, without having to add extra specifications like SOAP and UDDI. Any item can be made available (ie represented) at a URI, and, subject to the necessary permissions, it can be manipulated using one of the simple operations defined within HTTP (GET to retrieve information, PUT and POST to modify it, DELETE to remove it). Restians argue that retaining this very simple semantic structure is the best way of preserving interoperability between all Web participants.

highlights | A-Z index       


More about "REST" ...

Loosely Coupled articles:

The natives are RESTful
SOAP is not a prerequisite for web services. The alternative merits of REST are still being fiercely debated ...

When and how to use REST
Often times SOAP is overkill, and in those circumstances REST provides a simpler and more elegant solution ...

The trouble with SOAP
Ripples continue in the debate about whether SOAP is an over-engineered, unnecessary addition to the web services infrastructure ...

Useful Web resources:

Architectural Styles and the Design of Network-based Software Architectures
The PhD dissertation by Roy Fielding in which he coined the term REST

REST and the Real World
REST advocate Paul Prescod puts the case for building web services on REST principles

Discussion and resources site dedicated to all things REST.


Copyright © 2002-2010, Procullux Media Ltd. All Rights Reserved.