Andreas sent me a 6.6.3 snapshot that I believe has this feature.
I encountered the following problem: when started with -p 2033, the server failed to start with "Server is running or permission was denied." the log showed: "Address already in use".
Well, it turns out that address 2033 is not use, but an strace showed that the new version tries to bind to port 2033 and 1985, presumably in order to start the event service. Port 1985 is in use on my machine, however.
Suggestion: when encountering an exception in the ServerSocket constructor, print the port you were trying to bind to so the user knows what conflict to look for without having to resort to strace.
Lastly, even though I had started the server with -p 2033, it created a .basex file with these values: SERVERPORT = 1984 EVENTPORT = 1985 Shouldn't -p change the value of SERVERPORT when a .basex file is created?
- Godmar
On Tue, Jun 7, 2011 at 12:45 PM, Christian Grün christian.gruen@gmail.com wrote:
Dear all,
we're currently working hard to get Version 6.7 of BaseX finished. One of the major new features will be the support for database events, which can be triggered and received by any client:
http://docs.basex.org/wiki/Events
BaseX 6.7 will offer some other features, most of which are already available in the current snapshot..
http://files.basex.org/releases/latest/ https://github.com/BaseXdb/basex
Some of the new commands can be traced by comparing the old and new Command entry in our Wiki:
http://docs.basex.org/wiki/Commands http://docs.basex.org/wiki/Commands_(Snapshot)
If you have some early feedback, or if the current documentation does not cover all issues.. Feel free to contribute or give feedback.
All the best, Christian
PS: Another exciting feature we're currently implementing is the incremental update of all index structures. This feature will be available with BaseX 7.0. _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk