access to dom representation of result in server mode or with xqj
Tuesday, 12 February 2013 · 2 messages · last reply 13 Feb 2013
FE
Fabrice Etanchaud12 Feb 2013 15:40 #
Dear all at BaseX,
Is there a way to gain access the dom representation of a query result in server mode, or with xqj ? (in simple words, could a client side parser work directly on the internal server representation, for example by returning a 'eventified' serialization of the result ?)
Thank you for your wonderful NXDB !
Best regards,
Fabrice
CG
Christian Grün13 Feb 2013 13:50 #
Hi Fabrice,
yes, such a feature would be a fabulously interactive. Unfortunately, it would break our concurrency and transactions concept, because you’ll never know what users are about to do with those nodes.
Some current options to get better performance are:
– in embedded mode: switch to a more low-level approach: create QueryProcessor instances, work with the returned ANode/DBNode instances
– in embedded and client/server mode: use
db:node-id/pre() and db:open-id/pre() to request and open basex database nodes [1]
Hope this helps,
Christian
[1] http://docs.basex.org/wiki/Database_Module#db:open-idQuoted text · Fabrice Etanchaud · 27 lines
On Tue, Feb 12, 2013 at 3:40 PM, Fabrice Etanchaud <fetanchaud at questel.com> wrote: > Dear all at BaseX, > > Is there a way to gain access the dom representation of a query result in > server mode, or with xqj ? > > (in simple words, could a client side parser work directly on the internal > server representation, for example by returning a ‘eventified’ serialization > of the result ?) > > > > Thank you for your wonderful NXDB ! > > > > Best regards, > > Fabrice > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >
Written for BaseX 7.6. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery