Skip to content
This repository has been archived by the owner on Mar 22, 2018. It is now read-only.

Add support for locking resources #15

Open
brettatoms opened this issue Sep 2, 2013 · 1 comment
Open

Add support for locking resources #15

brettatoms opened this issue Sep 2, 2013 · 1 comment
Assignees
Milestone

Comments

@brettatoms
Copy link
Member

GET /family/1/lock - return true/false if the resource is locked
POST /family/1/lock - lock the resource, return true/false if the resource is successfully locked
GET /family/1 - with depth=2 return a locked property so we don't have to check for /lock

DELETE /family/1/lock - unlock the resource, return true/false if the resource is successfully unlocked, can only unlock a resource

POST /family/1 - return a 423 Locked if the resource is locked by another user

@ghost ghost assigned brettatoms Sep 2, 2013
@brettatoms
Copy link
Member Author

Also see Bauble/bauble.webapp#10

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant