• To: "'Mark Baker'" <distobj@a...>, costello@m...
• Subject: RE: Categories of Web Service messages: data-oriented vs action-oriented
• From: Michael Brennan <Michael_Brennan@A...>
• Date: Mon, 4 Feb 2002 14:35:48 -0800
• Cc: xml-dev@l...

> From: Mark Baker [mailto:distobj@a...]

<snip/>

> > I appreciate any clarity you can bring to this topic.  /Roger
> 
> You are well on your way to REST enlightenment. 8-)
> 
> Read back over the "Generality of HTTP" thread.  HTTP methods provide
> all the necessary "action" you'll ever need.

Not quite. HTTP will only let you express one action for the entire message.
We routinely use rich messages that bundle a number of actions together to
minimize network roundtrips. (I believe I've heard SOAP developers refer to
this as "box-carrying".) In addition, any one of those actions may
themselves contain nested actions that are evaluated within the context of
the containing action.

I don't see how you would express this purely at the HTTP layer.

• Follow-Ups:
  • Re: Categories of Web Service messages: data-oriented v
    • From: Mark Baker <distobj@a...>

• Prev by Date: Getting rid of entities (was: misprocessing namespaces)
• Next by Date: RE: Co-operating with Architectural Forms
• Previous by thread: RE: Categories of Web Service messages: data-oriented vs action-oriented
• Next by thread: Re: Categories of Web Service messages: data-oriented v
• Index(es):
  • Date
  • Thread