Dear Michael,
thanks for your observations. I see that our warnings cause some concerns that may have been substantial in previous versions, and I tried to soften them a little in our startup article [1]. The current status quo is actually quite safe:
· you will have a peaceful life if you open completely different databases · you may also safely open the same database for concurrent read operations · if you try to write to a database that has been opened by another virtual machine, you will get a warning, and the update will be canceled in due time
In a nutshell, the main restriction you will encounter is that update operations will be rejected if the target database has been opened by another process.
I hope this answer all questions, Christian
[1] http://docs.basex.org/wiki/Startup ______________________________________
At various points in the documentation, it is observed that the BaseX server, the BaseX client, and the GUI interface all run in different virtual machines, so the GUI and the server's databases are not synchronized.
In the GUI of BaseX 7.3, I see an optional Server Administration on the Database menu, which carries the warning
Warning: The client/server architecture and the GUI are not synchronized. The same database should not be opened from clients and the GUI.Does this mean that it's safe to run both the server and the GUI as long as they have different databases open? (It doesn't say that; it says it's unsafe if they have the *same* database open. You see how timid warnings can make a user!)
Also - in my case it would be convenient to be able to open the GUI and do some work while the BaseX HTTP server is running. If the HTTP server handles a request directed at database X, does that database remain open indefinitely or is it closed when the request has been handled? That is, is it safe to work with database X as long as I don't pass requests against X to the HTTP server at the same time/
And third - if neither the HTTP server nor the GUI are performing any updates, but only retrievals from the database, does the warning still apply, or is read-only access from multiple instances of BaseX actually safe?
(I ask because if I need to shut down the HTTP server every time I want to launch the GUI to experiment with a new function, and then shut down the GUI so I can launch the HTTP server and work on the Web interface to the new function, then I am going to want to find a more convenient way of starting and stopping the HTTP server than going into a terminal window and running the shell script.)
Thank you!
--
- C. M. Sperberg-McQueen, Black Mesa Technologies LLC
- http://www.blackmesatech.com
- http://cmsmcq.com/mib
- http://balisage.net
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk