- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 25 Oct 2008 01:40:26 +0200
- To: Jamie Lokier <jamie@shareable.org>
- CC: Helge Hess <helge.hess@opengroupware.org>, HTTP Working Group <ietf-http-wg@w3.org>
Jamie Lokier wrote: > Helge Hess wrote: >> On 21.10.2008, at 09:24, Julian Reschke wrote: >>>>> It would break existing clients, so I don't see how it could be >>>>> done in HTTP/1.1. >>>> Exactly which client are you talking about and how does it break? >>> For instance clients that do first a PUT-for-create, then a PROPPATCH. >> What happens in 'those' clients (_exactly_ which ones?!) when another >> client MOVEs the resource before the PROPPATCH. Thats a perfectly >> viable and normal situation. How is it different? > > That's what WebDAV's LOCK is for preventing, isn't it? LOCK can prevent that, but the likelihood of race conditions is small, so why bother? LOCK has a performance penalty (2 more roundtrips), and also is truly optional. BR, Julian
Received on Friday, 24 October 2008 23:41:08 UTC