Choreography and REST

For a REST perspective on choreography, Paul wrote this up recently.
IMO, it captures the essence of the problem perfectly;

http://www.ai.mit.edu/~gregs/ll1-discuss-archive-html/msg01848.html

When you move from an architecture with its own implicit state model
(REST has hypermedia as the engine of state change) to one without one
(the Web services architecture, as currently practiced - each object
has its own), you have these sorts of issues.

It's amazing how big an impact one little missing architectural
constraint can have. 8-)

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               [email protected]
http://www.markbaker.ca        http://www.idokorro.com