My scenario is: If there 1000 results from an index query, I would like to send 100 at a time to the requesting client(ie, browser). Which means browser will make 10 calls to get all the results by passing either the page number or the next start result(ie, 11, 21, 31 etc) in each call.
It looks like the PagingIterator seems to fit my scenario. Does the neo4j team recommend using the PagingIterator for this purpose? Appreciate all the responses. John On Wed, Jul 27, 2011 at 8:58 AM, John cyuczieekc <[email protected]>wrote: > Looks like John H. means, how do you get all results for page N and only > for > page N ? without the overhead of getting thru all other results; so far, as > I understand it (also from what Jim said), you'll have to parse all the > results for all pages prior to page N, to get to page N, but not the > results > after page N. > > On Wed, Jul 27, 2011 at 9:53 AM, Jim Webber <[email protected]> wrote: > > > Hi John, > > > > In an embedded scenario, pagination doesn't make as much sense. Since > calls > > to the embedded APIs typically return a lazily-evaluatable iterable<T> > you > > just call next() to efficiently advance through the results. > > > > Jim > > _______________________________________________ > > Neo4j mailing list > > [email protected] > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
