Hi Ralf,
yes, that's a good point. We'd probably have to check somewhere (e.g. in the HTTPSession.local() method) if a server exists in the same JVM. If you have a spontaneous idea how to perform this check.. Feel free to tell us ;)
Thanks, Christian
On Sat, Oct 15, 2011 at 2:21 PM, Ralf Jung ralfjung-e@gmx.de wrote:
Hi list,
while debugging my application, I noticed that when I send a request to the HTTP API of basex, the request is then sent by basex to itself via a localhost connection. That is, the HTTP API part of basex sends a message to the BaseX native API through TCP. Now, I wonder, is this really necessary? After all, both reside in the same process, so going through the OS feels a bit wasteful here. I noticed that I can change this behaviour if I pass the "-l" flag to basexhttp ("local mode"), so the code to directly use the in-process DB obviously exists. I wonder why it can only be used in the local mode which entirely disables the "native" BaseX API?
Kind regards, Ralf _______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk