Re: [Exist-development] [Exist-open] Performance of concurrent read queries.

[Jason S. <js...@in...>]

Adam, Wolfgang is correct.  The locking mechanism needed (useful) is tied to the database design.  In some designs, you don't need locks at all.  The current eXist design allows live writes (mutation), so you need locking to limit access.  The actual locking mechanism, however, could change significantly based on the underlying database implementation. 

-----Original Message-----
From: Wolfgang Meier [mailto:wol...@ex...] 
Sent: Thursday, September 02, 2010 6:43 AM
To: Adam Retter
Cc: Jason Smith; Paul Ryan; eXist development; Michael J. Pelikan; Todd Gochenour
Subject: Re: [Exist-development] [Exist-open] Performance of concurrent read queries.

> Is there not a whole class of lock free concurrent algorithms though?

As I said many times before: you cannot see locking in isolation. It
is tightly connected with transaction management, caching, log
sequence numbers, checkpoints and other concepts. Any change to
locking has to take all those other aspects into account.

Wolfgang