Hi Swaminathan,
in XQuery Update you can define and use a large number of xml's in an update, so it's pretty hard to define a good concurrency control which keeps up the good speed of BaseX and secures the queries too. So we decided to implement it as single writer. Maybe it will be enhanced to multiple writers in future releases. If you create your own concurrency controls, there shouldnt be any problems with updating different XMLs.
Kind regards, Andreas
Swaminathan S schrieb:
Hi Andreas,
You said: "All update queries will be queued and then processed one by one (doesnt mather on same or different xml)." Ideally, update queries on different xmls should be designed to run parallely? One of the reason I ask this is: Suppose I do not use server-client architecture(I use BaseX classes directly) and I introduce concurrency controls myself, should I expect any problems if I do concurrent writes on different XML?
Thanks,
Swaminathan Sahiram
On Mon, Mar 8, 2010 at 4:35 PM, Andreas Weiler <andreas.weiler@uni-konstanz.de mailto:andreas.weiler@uni-konstanz.de> wrote:
Hi Swaminathan, BaseX is handling requests as multiple reader and single writers. All update queries will be queued and then processed one by one (doesnt mather on same or different xml). Read queries will be processed simultaneous. I need to design the concurrency aspect. We would be pleased about your results. Kind regards, Andreas (BaseX Team)