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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Re: A question about REST and transaction isolation

[ Lists Home | Date Index | Thread Index ]
  • To: Pete Kirkham <pete.kirkham@baesystems.com>
  • Subject: Re: [xml-dev] Re: A question about REST and transaction isolation
  • From: Julian Reschke <julian.reschke@gmx.de>
  • Date: Wed, 11 Feb 2004 11:54:58 +0100
  • Cc: xml-dev@lists.xml.org, ari@cogsci.ed.ac.uk
  • In-reply-to: <"040211103051Z.WT03096. 15*/PN=Pete.Kirkham/OU=Technical/OU=NOTES/O=BAe MAA/PRMD=BAE/ADMD=GOLD 400/C=GB/"@MHS>
  • References: <"040211103051Z.WT03096. 15*/PN=Pete.Kirkham/OU=Technical/OU=NOTES/O=BAe MAA/PRMD=BAE/ADMD=GOLD 400/C=GB/"@MHS>
  • User-agent: Mozilla Thunderbird 0.5 (Windows/20040207)

Pete Kirkham wrote:
> From: 'ari@cogsci.ed.ac.uk@INTERNET@wtgw'(K. Ari Krupnikov)
>>User A GETs a resource and edits it. User B GETs a resource and edits
>>it. User A PUTs the modified resource back. User B PUTs her version of
>>the modified resource back, unaware of A's edits. A's edits are lost
>>without anyone noticing. What I want to happen is B to get a 409
>>"Conflict" or some such.
> This seems identical to the WebDAV use cases.
 > ...

A simple way to achieve this is just to use strong entity tags and HTTP 
If-Match headers when sending the PUT. This will avoid overlapping 
updates if all clients co-operate.

If this is not the case, WebDAV locks can be used as additional security 
measure (note that this will not help if A PUTs back after B is done).

Regards, Julian

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760


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

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