And you would want to reuse your connection so you don't have to pay this penalty per request
Just asking how would duch a REST Resource iterator look like -URI, verbs, request,response formats? I assume then evety query (index,traversal) would just return the iterator URI for later consumption. If we store the query and/or result information (as discussed by Crsig and others) at the "node" returned as iterator this would be a nice fit. M Sent from my iBrick4 Am 22.04.2011 um 19:46 schrieb Jim Webber <j...@neotechnology.com>: > Hi Georg, > > It would at least have to be an iterator over pages - otherwise the results > tend to be fine-grained and so horribly inefficient for sending over a > network. > > Jim > > On 22 Apr 2011, at 18:24, Georg Summer wrote: > >> I might be a little newbish here, but then why not an Iterator? >> The iterator lives on the server and is accessible through the REST >> interface, providing a advance and value method. It either operates on a >> stored and once-created-stable result set or holds the query and evaluates >> it on demand (issues of changing underlying graph included). >> >> The client can have paginator functionality by advancing and derefing the >> iterator n times or streaming-like behaviour by constantly pushing the >> obtained data into a queue and keep on going. >> >> If the client does not need the iterator anymore he simple stops using it >> and a timeout kills it eventually on the server. a client-callable delete >> method for the iterator would work as well. >> >> >> Georg > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
