Hi Huib,
an intermediate update: yes, I should have parsed your mail until the very bottom..
[...] When we use only one thread (simulated user) everything is fine, when we increase the number of threads we quickly end up with a corrupted database [...]
I know it’s no easy task, but if you manage to create a reproducible use case (the easier/smaller the better), that would be great.
I would much appreciate a wiki-per-version, e.g. a 7.3 wiki, a7.4 wiki, etc.
Copying the whole Wiki with every release feels like a greater effort, which is why we have decided to create PDF versions, which can also be retrieved for older versions [1,2,..]. Does this help? The most elegant solution, in my point of view, would be if you could browse past „snapshot” of the documentation. Unfortunately, although it uses revisions, the MediaWiki software does not allow this.
the mailing list search service on the basex.org website (linksfrom the “Open Source” page) crashes.
True, and thanks, I'll have a look at that. We're about to switch to a new version of the homepage, which will be completely built in XQuery; the problems should then be gone.
[1] http://files.basex.org/releases/7.2/BaseX72.pdf [2] http://files.basex.org/releases/7.2.1/BaseX721.pdf
(7.4) I am confused about the org.basex.restxqpath vs.org.basex.webpath settings, I put them both in and then it seemed to work. (Perhaps db:system() is also inconsistent wrt these settings.) RESTXQPATH is not mentioned in the OPTIONS list.
Those changes are very fresh, which is why we haven’t updated all pages of the documentation yet. In future, WEBPATH will point to the webapp directory, whereas the additional RESTXQPATH variable can point to an alternative path.
I also used db:system() and had to adapt that too because org.basex.httppath no longer exists.
Out of interest: For what reason do you access/utilize this particular option? Christian