[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

REST and HTTP extensions (was Re: Re: Why REST? )

• To: xml-dev@l...
• Subject: REST and HTTP extensions (was Re: Re: Why REST? )
• From: Mike Champion <mc@x...>
• Date: Mon, 11 Feb 2002 16:59:10 -0500
• In-reply-to: <2C61CCE8A870D211A523080009B94E4306FEE85C@HQ5>

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 ...

• Follow-Ups:
  • Re: REST and HTTP extensions (was Re: Re: Why REST? )
    • From: Paul Prescod <paul@p...>
  • Re: REST and HTTP extensions (was Re: Re: Why REST? )
    • From: John Cowan <cowan@m...>

• References:
  • RE: Re: Why REST? (RE: WSIO- With Name)
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: REST has too many verbs
• Next by Date: Re: REST has too many verbs
• Previous by thread: Re: Re: Why REST? (RE: WSIO- With Name)
• Next by thread: Re: REST and HTTP extensions (was Re: Re: Why REST? )
• Index(es):
  • Date
  • Thread