| From | Sent On | Attachments |
|---|---|---|
| K. Ari Krupnikov | Feb 8, 2004 4:59 pm | |
| David Megginson | Feb 8, 2004 5:42 pm | |
| K. Ari Krupnikov | Feb 8, 2004 8:58 pm | |
| Seairth Jacobs | Feb 9, 2004 5:45 am | |
| Seairth Jacobs | Feb 9, 2004 5:51 am | |
| David Megginson | Feb 9, 2004 6:21 am | |
| Bullard, Claude L (Len) | Feb 9, 2004 7:07 am | |
| Bullard, Claude L (Len) | Feb 9, 2004 7:43 am | |
| David Megginson | Feb 9, 2004 8:19 am | |
| Bullard, Claude L (Len) | Feb 9, 2004 8:26 am | |
| K. Ari Krupnikov | Feb 9, 2004 11:35 am | |
| K. Ari Krupnikov | Feb 9, 2004 1:00 pm | |
| Bullard, Claude L (Len) | Feb 9, 2004 1:45 pm | |
| K. Ari Krupnikov | Feb 9, 2004 2:43 pm | |
| Bullard, Claude L (Len) | Feb 9, 2004 2:51 pm | |
| Jim Ancona | Feb 9, 2004 3:04 pm | |
| David Megginson | Feb 9, 2004 4:46 pm | |
| Seairth Jacobs | Feb 9, 2004 6:24 pm | |
| K. Ari Krupnikov | Feb 10, 2004 9:54 pm | |
| K. Ari Krupnikov | Feb 10, 2004 10:13 pm | |
| Pete Kirkham | Feb 11, 2004 2:26 am | |
| Julian Reschke | Feb 11, 2004 2:54 am | |
| Klotz, Leigh | Feb 11, 2004 10:18 am | |
| Robin Berjon | Feb 11, 2004 10:21 am | |
| Chiusano Joseph | Feb 26, 2004 6:18 am | |
| Michael Champion | Feb 26, 2004 7:29 am | |
| Bullard, Claude L (Len) | Feb 26, 2004 7:51 am |
| Subject: | Re: [xml-dev] Re: A question about REST and transaction isolation | |
|---|---|---|
| From: | Julian Reschke (juli...@gmx.de) | |
| Date: | Feb 11, 2004 2:54:36 am | |
| List: | org.xml.lists.xml-dev | |
Pete Kirkham wrote:
From: 'ar...@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





