OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   REST and HTTP extensions (was Re: [xml-dev] Re: Why REST? )

[ Lists Home | Date Index | Thread Index ]

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 operator (sortof a LOCK, 
GET, DELETE transaction)?  

I can see how to model these with REST, i.e.,a series of GET, POST, DELETE operations and 
some logic to test for the existence of lock resources or metadata.  But 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 ...


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS