kranga wrote:
Hi, What does the spec say in relation to the following scenario:
- You have a collection A that is locked. You create a lock-null resouce under A called foo.bar. Now, this has to be created using a LOCK method execution and you are likely to get a different token or the same token as the parent collection.
I think you should not be able to create a lock-null resource under a locked collection. To work on a locked resource (e.g. to add a new member using MKCOL) you have to provide the locktoken in the If header. But with the LOCK method the If header is used for refreshing locks (s. 7.8), so I would say you cant lock under a locked resource. Thats clear for existing resource and I think it is valid for Lock-Null resources to. I'm not sure we have a test case that veriyfies that. I will have a look, ASAP.
The webdav specs say that any child of a collection that is locked (by default with depth infinity) should also be automatically added to that lock. However, if you create it with the same locktoken as the parent, then an unlock on the parent collection will make the lock-null resource vanish, which may not be desirable. However, if you create it with a different lock-token, then it is against the spec that children of a locked collection should be part of that lock. So do you create multiple locks? One for the lock-token and one for the collection? In that case how do you honor a PUT or MKCOL on it? I think you can only specify one lock in the lock-token header??? What if you only support exclusive locks?
Thanks K
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
