Hi Christian
JAX-RX and BaseX
Want to be sure, that indexes will be updated after collection has been modified and no one will have a chance to run a query on not optimized collection
Want to be sure, that indexes will be updated after collection has been modified and no one will have a chance to run a query on not optimized collection
It is better to quit too long query then risking that one too expensive query would endanger overall server performance
There is no need to get query results too late, when our http connection already timed out
> OK, I understand, that REST allows to perform the (SET) command, but to useJust recently, I've thought about extending the JAX-RX Interface to
> it with a query, I have to send the query in another, following, request.
> Will this second request keep enough context at the server side to know, it
> shall use that timeout?
allow more than a single query or command, or to allow both commands
and queries; regarding the syntax, this could be easily realized for
the GET method:
http://localhost:8984/basex/jax-rx/factbook?query=1&query=2
http://localhost:8984/basex/jax-rx/factbook?command=set+timeout+1&query=1&command=info
On the other hand, I haven't decided yet how to best realize it for
the POST method without giving up compatibility. One solution could be
to introduce alternative "request" root elements:
<request xmlns="http://jax-rx.sourceforge.net">
<command>
<text>set timeout 1</text>
</command>
<query>
<text>//name</text>
<parameter name="count" value="5"/>
</query>
</request>
What does everyone think?
Christian
_______________________________________________
BaseX-Talk mailing list
BaseX-Talk@mailman.uni-konstanz.de
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk