I believe this has been fixed now, so download and try with the latest rest
server, http://wiki.neo4j.org/content/Getting_Started_REST
2010/4/13 Alastair James al.ja...@gmail.com
Cheers. Sorry, I probably should have filed this in the Trac.
Al
On 13 April 2010 00:15, Tobias Ivarsson
You mean using the Content-Type/Accept headers? That's at least how it's
solved now with text/html and application/json living side to side in the
REST API today.
2010/3/23 Jim Webber j...@webber.name
Just another thought: if we're going to use multiple representation
formats, then we should
Forgot to CC the mailing list
-- Forwarded message --
From: Mattias Persson matt...@neotechnology.com
Date: 2010/4/21
Subject: Re: Feedback request
To: Niels Hoogeveen pd_aficion...@hotmail.com
Cc: Neo Devteam devt...@neotechnology.com
I'd say go for it, but you could bump the
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
Hi Mattias,
Yeah, that's what I meant. I really should update my source one of these days...
Jim
On 21 Apr 2010, at 11:11, Mattias Persson wrote:
You mean using the Content-Type/Accept headers? That's at least how it's
solved now with text/html and application/json living side to side in the
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
The better approach is to use an optional request parameter (which
is unlikely to conflict with real request parameters) that provides
the necessary value(s) that the headers provide, which is analogous to
the mechanism used by most REST APIs to allow browsers to do PUT,
DELETE,
I got the same thing:
Here is my answer to your post:
I agree with you completely, and i am trying to get the best of
both worlds. Maybe bytecode manipulation is the only way to
go
But are you in fact saying that i am implementing an
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 per
I agree with your observations and changed the names of the
classes/interfaces/enumerations to ...Property... and ...Relationship
I have pushed back a lot of the code duplication, which I wasn't too happy with
either. MetaModelRestrictable now has a type parameter with respect to the
Couldn't this mess up caching?
Jim
PS - Query params should be considered part of a URI, I dislike that RFC2616
says dumb things about them.
On 21 Apr 2010, at 13:18, rick.bullo...@burningskysoftware.com wrote:
The better approach is to use an optional request parameter (which
is
On Wed, Apr 21, 2010 at 2:56 PM, Atle Prange atle.pra...@gmail.com wrote:
I got the same thing:
Here is my answer to your post:
I agree with you completely, and i am trying to get the best of
both worlds. Maybe bytecode manipulation is the only way to
go
2010/4/21 Niels Hoogeveen pd_aficion...@hotmail.com
I agree with your observations and changed the names of the
classes/interfaces/enumerations to ...Property... and ...Relationship
I have pushed back a lot of the code duplication, which I wasn't too happy
with either.
The updates are in SVN now.
Date: Wed, 21 Apr 2010 16:43:12 +0200
From: matt...@neotechnology.com
To: user@lists.neo4j.org
Subject: Re: [Neo] Fwd: Feedback request
2010/4/21 Niels Hoogeveen pd_aficion...@hotmail.com
I agree with your observations and changed the names of the
The first draft i have implemented is the wrapper approach:
Entities must subclass NodeWrapper, and typed relations RelationshipWrapper.
These superclasses can get a context set on them, which contains the graph
element they wrap.
I added some helper classes that makes the setting and getting of
15 matches
Mail list logo
