>> > > Moreover, is this double search really necessary? It looks like the records > can be returned already at the first search. In particular, when the search > is to get more results for the same query (over the initial 100) the first > search was already done before. So why doesn't this work: > > - When availableResults and fetchedResults were both 0 (initial search for > new search term), try to get the first MAX_RESULTS immediately, and update > availableResults and fetchedResults from the returned data. > - When they're not 0 (i.e. get more for the same search) get the next batch > of MIN(availableResultsLocal - fetchedResultsLocal, MAX_RESULTS), if that's > bigger than 0. > > From the docs it seems that the second case could be done more easily using > the retrieve operation using the queryID, but in my tests the queryID never > seems to be returned.
I'll check that double search issue before committing my code. Reto ------------------------------------------------------------------------------ _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
