- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Wed, 30 Jun 2004 11:14:05 -0700
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: WebDAV <nnw3c-dist-auth___at___w3.org@smallcue.com>
Yes, I read these today, but it was my interpretation that this testing applied to the UNLOCK request. What about LOCK request to refresh a lock? Does that also work on resources other than the lock root? I think servers would probably implement them the same way, but I was curious whether you'd tested it explicitly. Lisa On Jun 30, 2004, at 11:08 AM, Julian Reschke wrote: > Lisa Dusseault wrote: >> Hey, I forgot to ask. Julian, in your research, did you happen to >> test LOCK to refresh a lock as well? Do server implementations allow >> LOCK on any resource-URI within the scope to successfully refresh the >> lock? > > Yes, I did. See > <http://greenbytes.de/tech/webdav/draft-reschke-webdav-locking- > issues.html#065_UNLOCK_WHAT_URL> and in particular: > <http://lists.w3.org/Archives/Public/w3c-dist-auth/2004AprJun/ > 0170.html>. > > -> Servers do not care about whether the resource is directly or > indirectly locked. > > Julian > > -- > <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Wednesday, 30 June 2004 14:14:41 UTC