> 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, proc
Hi Aseem,
> Jim, thanks for the explanation. I understand your constraints, but thinking
> about it more, I'm actually even more baffled -- how can we actually make
> use of this paged traversal API in a web scenario?
Neo4j's traversers (which is what the REST paging API really is) knows nothing
:user-boun...@lists.neo4j.org]
> On Behalf Of Aseem Kishore
> Sent: Thursday, July 28, 2011 6:42 PM
> To: Neo4j user discussions
> Subject: Re: [Neo4j] Paged traversal REST API suggestion for improvement
>
> Sorry, I don't understand. Are you going to tell Google and Bing to s
uly 28, 2011 6:42 PM
To: Neo4j user discussions
Subject: Re: [Neo4j] Paged traversal REST API suggestion for improvement
Sorry, I don't understand. Are you going to tell Google and Bing to send
JSON for their search results also, and page on the client side? There is a
very valid use case f
> To: Neo4j user discussions
> Subject: Re: [Neo4j] Paged traversal REST API suggestion for improvement
>
> Sure but isn’t it a huge waste of bandwidth if you load hundreds of results
> and the user only looks at the first dozen?
>
> On Thu, Jul 28, 2011 at 15:16, Rick Bullotta
t: Re: [Neo4j] Paged traversal REST API suggestion for improvement
Sure but isn’t it a huge waste of bandwidth if you load hundreds of results
and the user only looks at the first dozen?
On Thu, Jul 28, 2011 at 15:16, Rick Bullotta wrote:
> BTW, "paging" is a relic of the dial-up
ata in a single call.
>
> -Original Message-
> From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org]
> On Behalf Of Rick Bullotta
> Sent: Thursday, July 28, 2011 6:11 PM
> To: Neo4j user discussions
> Subject: Re: [Neo4j] Paged traversal REST API suggesti
ssions
Subject: Re: [Neo4j] Paged traversal REST API suggestion for improvement
If you don't keep "state" paging will not work properly if the data changes
often. What may have been record #21 when you are viewing the first page of 20
result might not be record #21 when you
, and won't require any "state".
-Original Message-
From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On
Behalf Of Aseem Kishore
Sent: Thursday, July 28, 2011 3:01 PM
To: Neo4j user discussions
Subject: Re: [Neo4j] Paged traversal REST API suggestion for
Jim, thanks for the explanation. I understand your constraints, but thinking
about it more, I'm actually even more baffled -- how can we actually make
use of this paged traversal API in a web scenario?
[neo4j db] < [web server] < [web client, e.g. browser]
If I want to show the results of
Hi Aseem,
When you GET a resource, you're asking for its state at a particular instant in
time. GET's don't always return the same content, what's important about them
is that clients can't be held responsible for any (unintended) side-effects of
a GET operation. For example, if you GET the BBC
Hey there,
Neo4j's REST API is overall quite awesome and impressive -- it's just such a
great *actual* REST API.
I was just reading into paged traversals (
http://docs.neo4j.org/chunked/stable/rest-api-traverse.html ) and couldn't
help but feel that this isn't the best way to do paging over REST.
12 matches
Mail list logo
