Though, whenever httpserver (via restxq) tries to reach the DB, the distant
server log shows these lines:
17:00:10.384[10.129.63.247:45084] LOGIN log OK
17:00:11.623[10.129.63.247:45084] LOGOUT log OK
'log' is the user name.
But that's all.
Gilles.
> -Original Message
Dear Mike,
currently, all server operations are logged as plain text and
shortened to a maximum of 1000 characters per single command. If you
want to have more control on logging, and provide it on a higher
level, you can e.g. use functions like file:append() to write your own
logs to disk [1].
W
Hi Andy,
> 1) The documentation at http://docs.basex.org/wiki/Server_Protocol shows
> nothing in the Server Response column. This seems not to be the case. It
> looks like a standard BaseX protocol type response is to be expected?
yes you are right, the server response is a standard basex info
Am Mittwoch, 16. Mai 2012, 19:52:45 schrieb Philippe Rathé:
> Then do we need to run a BaseXServer using RESTXQ?
No, you don't need to run a separate BaseXServer if you want
to use RESTXQ, since as already said, RESTXQ in BaseX can
access only local databases (or at least that is what I'm aware
of
Hi,
I am looking at adding WATCH and UNWATCH to my Node.js BaseX interface and
I have a couple of questions before I start.
1) The documentation at http://docs.basex.org/wiki/Server_Protocol shows
nothing in the Server Response column. This seems not to be the case. It
looks like a standard BaseX
5 matches
Mail list logo
