aka REST, for Representational State Transfer.

• Representation: a Resource (identified by URI) can have multiple representations (XML, HTML, JSON, RSS, etc.)

• a CRUD Update is requesting a Resource to change its State (State Machine)

  • many interactions are more complex than a CRUD, but are still a State change. REST components perform actions on a resource by using a representation to capture the current or intended state of that resource and transferring that representation between components.

    • z2006-07-01- Dhh World Of Crud

    • z2006-11-17- Rest Vs Soap Again

    • z2007-01-12- Downey Website Api maybe

http://www.xml.com/pub/a/2002/02/06/rest.html

http://rest.blueoxen.net/cgi-bin/wiki.pl?FrontPage

http://www.xfront.com/REST-Web-Services.html

excellent explanation of the value/simplicity of ReST and HTTP.

the [FAQ] includes some interesting notes on application of REST approach to things you wouldn't normally associate HTTP with - e.g. Instant Messaging, and compares it to SOAP.

one key concept is that each schema stays focused on just describing some data - then when add different functions/requirements, you just pass that data to a new URI associated with that transaction. That smells like a nice thing...

http://www.soundadvice.id.au/blog/2006/09/29/#commonRESTQuestions

PyThon and ReST

and AJAX http://www.onlamp.com/pub/a/python/2006/02/23/using-rest-with-ajax.html

Joe Gregorio, example URI-s http://www.xml.com/pub/a/2005/08/17/restful-web.html

QuiXote http://www.rexx.com/~dkuhlman/rest_howto.html

ZoPe support http://www.vanpyz.org/conference/2006/proceedings/8rMJUi/RestZope.html

User Options Recent Changes Help Page