Re: [Neo] Relationship representation in REST

2010-04-26 Thread Brian Turner
Configurable per request sounds reasonable. If one could select which properties to return, that would be great, however, the options "all", or "none", would be sufficient for most use cases I would think. B. __ Brian Turner http://wodaklab.org 4

Re: [Neo] Relationship representation in REST

2010-04-26 Thread Rick Bullotta
lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Mattias Persson Sent: Monday, April 26, 2010 4:13 AM To: Neo user discussions Subject: Re: [Neo] Relationship representation in REST Is there any kind of consensus here? Always send back full node representation? Not send back full node

Re: [Neo] Relationship representation in REST

2010-04-26 Thread Mattias Persson
Is there any kind of consensus here? Always send back full node representation? Not send back full node representation? Configurable per request somehow? 2010/4/21 Brian Turner > > I would have to agree. I've been trying out the REST interface, and it > > would > > be nice to have the option to

Re: [Neo] Relationship representation in REST

2010-04-21 Thread Brian Turner
> I would have to agree. I've been trying out the REST interface, and it > would > be nice to have the option to have the full details of each node returned > when doing a traversal. > >>You say have the "option" to have the full details? I'd rather not have it >>configurable per server... maybe p

Re: [Neo] Relationship representation in REST

2010-04-21 Thread Mattias Persson
Yep and that also brings in the discoverability features... (I get the fealing I'm going to get bashed though). As it is now I'd say at least 50% of the data is just links provided back for the sake of discoverability. Will people actually use those template URIs? I think not many will... and if t

Re: [Neo] Relationship representation in REST

2010-04-21 Thread Jim Webber
Hi Mattias, There are use cases where the REST API shouldn't be chatty - using HTTP caching you effectively build up a local representation of a graph over time. At the moment we don't have any specific cache headers (AFAIK) which means that clients are allowed to cache representations for as l

Re: [Neo] Relationship representation in REST

2010-04-21 Thread Mattias Persson
is more specific > > than "Re: Contents of User digest..." > > > > > > Today's Topics: > > > > 1. Relationship representation in REST (Mattias Persson) > > > > > > -- > > > > Message: 1 > > Date: Wed, 21 Apr 2010 11:57:01 +0200 &g

Re: [Neo] Relationship representation in REST

2010-04-21 Thread Brian Turner
y's Topics: > > 1. Relationship representation in REST (Mattias Persson) > > > -- > > Message: 1 > Date: Wed, 21 Apr 2010 11:57:01 +0200 > From: Mattias Persson > Subject: [Neo] Relationship representa

[Neo] Relationship representation in REST

2010-04-21 Thread Mattias Persson
I started a shell on top of a RestGraphDatabase (laboratory implementation of a GraphDatabaseService which communicates via the REST API) yesterday and I saw how "chatty" it needed to be to be able to do its stuff. More chatty = huge overhead in request latence of course. So I though one rather rea