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

Resources should be locked when open for editing #10

Open
brettatoms opened this issue Jan 3, 2013 · 1 comment
Open

Resources should be locked when open for editing #10

brettatoms opened this issue Jan 3, 2013 · 1 comment
Milestone

Comments

@brettatoms
Copy link
Member

When an editor is opened on a resource then the server should be notified that it is open for editing and should prevent future changes to the same resource until it is unlocked. It could be as easy as visiting, .e.g. /family/1/lock and /family/1/unlock to lock and unlock a resource.

A table should be created to hold the locked states that includes the user who locked it, the time it was locked and probably other meta data about the lock.

We also need a mechanism to forcefully break locks.

@brettatoms
Copy link
Member Author

Also see Bauble/bauble.api#15

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