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
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
...
e.g.
someURL?_acceptHeaders=text/xml;application/thingworx;bloodtype/apos
Original Message
Subject: Re: [Neo] Conneg in REST API
From: Jim Webber j...@webber.name
Date: Wed, April 21, 2010 7:00 am
To: Neo user discussions user@lists.neo4j.org
;bloodtype/apos
Original Message
Subject: Re: [Neo] Conneg in REST API
From: Jim Webber j...@webber.name
Date: Wed, April 21, 2010 7:00 am
To: Neo user discussions user@lists.neo4j.org
Hey Peter,
If we really want to cater for non-compliant
Just another thought: if we're going to use multiple representation formats,
then we should use content negotiation.
Jim
___
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
5 matches
Mail list logo