[jcifs] Davenport Locking

eglass1 at comcast.net eglass1 at comcast.net
Wed Mar 3 10:29:50 GMT 2004

> Also note that creating a WebDAV lock both locks the resource identified 
> by the request URI (directly), and the URI itself (indirectly). For 
> instance, after having locked "a/b" you are not supposed to be able to 
> rename "a" without providing the lock token in the request header. This 
> may be possible to enforce in the servlet, but probably not via SMB.

As another example, you can also (I *think*) lock a URI that does not currently
map to a resource (i.e., a nonexistent file which is intended to be created
in the near future).  This would definitely need to be managed "artificially"
by the servlet.


More information about the jcifs mailing list