> In Slide 2.0 locking for concurrency was done exclusively in the > physical store, which in your scenario would be MySQL. This used to > frequently cause a number of deadlocks. In 2.1 there is additional > locking in the WebDAV layer, that prevents deadlocks. However, > sometimes it is too restrictive which has been relaxed in what > eventually will be 2.2
Do you feel that the WebDAV API would be appropriate for my use case (up to several hundred concurrent users reading from and writing to the repository on a remote server)? I've been meaning to do some basic concurrency testing using JMeter to simulate our requirements. When I get around ti running the tests, I'll post my results to this list. > 2.1 is more mature concerning MySQL support, specifically MySQL 4.1. > It also supports transactions controlled by WebDAV, plus many fixes. I > might repeat myself, but there are many people saying that even now > 2.1 is more mature than 2.0. That's very encouraging. I'll continue to use 2.1 for my tests and plan on using it in production. What is the estimated release date for 2.1 at this point? Do you plan on having another beta release first? I didn't find any information on this on the roadmap. -Mirko --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
