[EMAIL PROTECTED] wrote:
Has anyone written a better iterator service for Xindice/Xml:db to get over the limitation of throwing an out-of-memory exception if your
Xpath query returns too many results?
It seems that the default behaviour for Xindice at least, is to return ALL the results in the ResourceIterator instead of using some
server-side paging mechanism, so our xindice client code regularly gets nasty out of memory exceptions..
Since we have noe way of knowing if an Xpath is going to return large result sets or not, I would have thought this would be a natural behaviour
for listing/querying a collection.
Anyone have any other ideas to approach this problem?
Does it return all the documents? Or keys only? One idea is to return only keys, this should help a lot.
Vadim
