I have a query that works through many documents looking for certain
elements/values (basically, cross references to other documents). It
first creates a new document for logging results. For each
cross-reference found, the query updates the log document by adding a
new element as a child. It also increments a counter in a server field.
The query can run for a while - there is a lot of content to go through,
and it is a web application, so I'd like to let the user know how the
query is coming along. So a separate query is initiated as an Ajax
request that should return the contents of the server-field. Some
javscript on the browser uses the response from that second query to
update a progress bar in the browser.
The problem is, the second query (the Ajax request for the contents of
the server field) won't start until the first query (the main one) is
finished. I've fooled with any number of techniques, including wrapping
the inner portions of the first query inside xdmp:eval wrappers to
isolate the update transactions and also spawning the query. Neither
works (well, not quite accurate - the spawn allows the second ajax query
to run, but it doesn't access the server-field, under spawn, the query
seems to have its own server fields?).
Any suggestions? What am I missing here.
--
/Steve/
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general
