Lists Home |
Date Index |
- To: "Mike Champion" <email@example.com>,<firstname.lastname@example.org>
- Subject: RE: [xml-dev] REST and HTTP extensions (was Re: [xml-dev] Re: Why REST? )
- From: "Joshua Allen" <email@example.com>
- Date: Tue, 12 Feb 2002 17:15:24 -0800
- Thread-index: AcG0EZMW98BranLPRkSVGer1Nep/IgAGiAkw
- Thread-topic: [xml-dev] REST and HTTP extensions (was Re: [xml-dev] Re: Why REST? )
I think WebDAV was specifically mentioned in the Fielding dissertation
about REST, as being a rest-ian thing. He says that the resource
retrieved by HTTP is never the actual resource, but instead is a
mediated view, but he goes to pains to point out that a mediated view
comes from a base resource and should in most cases be modifiable.
> -----Original Message-----
> From: Mike Champion [mailto:firstname.lastname@example.org]
> Sent: Monday, February 11, 2002 1:59 PM
> To: email@example.com
> Subject: [xml-dev] REST and HTTP extensions (was Re: [xml-dev] Re: Why
> REST? )
> One thing that doesn't seem to have come up in this mega-thread is how
> REST relates to
> things like WebDAV (which adds a few more verbs to HTTP to make
> collections of resources,
> lock and unlock resources, add metadata to a resource, copy and move
> resources between
> collections). Also, what about things like the tuple-space TAKE
> (sortof a LOCK,
> GET, DELETE transaction)?
> I can see how to model these with REST, i.e.,a series of GET, POST,
> operations and
> some logic to test for the existence of lock resources or metadata.
> does bundling
> these into sequences of operations that are performed as a transaction
> violate REST, or
> merely extend HTTP?
> Sorry if this is a painfully stupid question ...
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>