1 package com.bradmcevoy.http;
2
3 /**
4 * (from the spec)<BR/>
5 * <B>7.4 Write Locks and Null Resources</B>
6 * <P/>
7 * It is possible to assert a write lock on a null resource in order to lock the name.
8 * <P/>
9 * A write locked null resource, referred to as a lock-null resource, MUST respond with
10 * a 404 (Not Found) or 405 (Method Not Allowed) to any HTTP/1.1 or DAV methods except
11 * for PUT, MKCOL, OPTIONS, PROPFIND, LOCK, and UNLOCK.
12 * <P/>
13 * A lock-null resource MUST appear
14 * as a member of its parent collection. Additionally the lock-null resource MUST have
15 * defined on it all mandatory DAV properties. Most of these properties, such as all
16 * the get* properties, will have no value as a lock-null resource does not support the GET method.
17 * Lock-Null resources MUST have defined values for lockdiscovery and supportedlock properties.
18 * <P/>
19 * Until a method such as PUT or MKCOL is successfully executed on the lock-null resource
20 * the resource MUST stay in the lock-null state. However, once a PUT or MKCOL is
21 * successfully executed on a lock-null resource the resource ceases to be in the lock-null state.
22 * <P/>
23 * If the resource is unlocked, for any reason, without a PUT, MKCOL, or similar method
24 * having been successfully executed upon it then the resource MUST return to the null state.
25 *
26 *
27 */
28 public interface LockNullResource extends PutableResource, PropFindableResource, LockableResource {
29 }