Delete Private Lock

Once the resource has been updated (or if the update is to be abandoned for some reason) the client can release the lock by submitting a DELETE request to the private lock URI:

curl --include -u username:password -X DELETE http://host-ip-address/webservice/escenic/lock/article/4/private/9

If the DELETE request succeeds, then the web service returns a 204 No Content response:

HTTP/1.1 204 No Content
Server: Apache-Coyote/1.1
Date: Sat, 04 Dec 2010 02:57:09 GMT

It is possible to force the release of a lock held by another client by submitting a DELETE request to the public lock URI:

curl --include -u user:password -X DELETE http://host-ip-address/webservice/escenic/lock/article/4/public/39

If the DELETE request succeeds, then the web service returns a 204 No Content response:

HTTP/1.1 204 No Content
Server: Apache-Coyote/1.1
Date: Sat, 04 Dec 2010 03:09:38 GMT

If a client fails to delete a private lock URI, the lock will be released by the web service after 24 hours. To keep a resource locked for longer than this, a client must release its lock and immediately acquire a new one.