> All of this works, without JS. That means the client (your browser) isn't > the party doing the paging or keeping track of all results. It's something > on the server side.
That "something on the server side" is called "Google". That is, there is an organisation which has set up databases, processing, caching, and a myriad of other things and exposed them through a Web server. Saying Neo4j should do this because Google does isn't a fair comparison - Google has more than a database, it has an entire application. I'd say your app should do this, and if you can find a performant way of doing it that doesn't hold server-side state then I'll be happy to take a patch for the REST API. Jim _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user