From: Adam R. <ad...@ex...> - 2011-08-10 10:24:26
|
Dannes, So what did you make of my proposals (August 8th) for changes to the code, and can you comment on why we release the internal READ lock but tell WebDAV that its locked - that seems dangerous to me, but there are probably some webdav specific reasons? On 10 August 2011 11:56, Dannes Wessels <da...@ex...> wrote: > Hi, > > On Wed, Aug 10, 2011 at 11:08 AM, Adam Retter <ad...@ex...> wrote: >> >> > I think this is actually working correctly. The function puts a user >> > lock >> > and a lockToken on the resource, which (from my understanding) is the >> > correct way to put a persistent (user level) lock on a document. >> >> I think that lockToken is only used for WebDAV and nothing else unless >> I am mistaken? > > yes it is right. it is a 'symbolic' representation of a lock, but it does > not actually perform any locking.... > >> >> > What it's >> > releasing is the database READ_LOCK, which can block other processes >> > that >> > try to read the resource. >> >> READ_LOCK does not block other reads, it only blocks other writes. > > jups.... > > D. >> >> -- >> Adam Retter >> >> eXist Developer >> { United Kingdom } >> ad...@ex... >> irc://irc.freenode.net/existdb >> >> >> ------------------------------------------------------------------------------ >> uberSVN's rich system and user administration capabilities and model >> configuration take the hassle out of deploying and managing Subversion and >> the tools developers use with it. Learn more about uberSVN and get a free >> download at: http://p.sf.net/sfu/wandisco-dev2dev >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development > > > > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |