Hi everyone!
I have a nice idea, how to stop to crack the database, when user use GUI and server simultaneously. When GUI will found launched server, every updating functions should be executed through port, not directly.
User may setup different connections (require list of connections), select the default connection, and choose method of connection: direct access or via saved one
Sorry for my bad English.
Alexander
Hi Alexander,
I have a nice idea, how to stop to crack the database, when user use GUI and server simultaneously. When GUI will found launched server, every updating functions should be executed through port, not directly.
the problem here is that the GUI and the database backend are tightly coupled. During the visual construction of the Map View, for example, thousands of atomic database requests are performed, which would be much too slow when being realized through a socket connection.
The way it‘s implemented now, it should (hopefully) be difficult enough to corrupt existing databases, but the obvious restriction is that no updates will be possible whenever another JVM has opened the same database.
Christian
basex-talk@mailman.uni-konstanz.de