Hi there,
I am currently thinking about ways how to model a reliable checkout-checkin scenario with XML documents.
In an older SGML CMS system that we build, we implemented the procedure roughly like that:
- user chooses a document in the CMS and clicks on CHECKOUT - CHECKOUT copy the document to a private area of the user - CHECKOUT will lock the original file (reads allowed, write forbidden) - user edits the the copied content - user performs either a CHECKIN which will copy the private copy of the file into its original location and release the lock - or user will cancel the checkout (removing the copy and releasing the lock)
I see that exist-db has support for read and exclusive locks (inside the util: module).
Can they be used to implement such a scenario?
Is it possible to associate (arbitrary metadata) with locks like lock time, user who created the lock, app specific data?
Is it possible to introspect all current locks on the database?
Is there something like a lock token (in WebDAV) does one needs to release a lock?
Andreas