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, etc...



   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>
   Hey Peter,
   If we really want to cater for non-compliant browsers, then we can
   dispatch on user-agent, using the same XHTML code that exists today.
   Jim
   On 21 Apr 2010, at 11:18, Peter Neubauer wrote:
   > Yeah,
   > this is good, except that some browsers, e.g. IE, don't provide these
   > headers and thus f... up all that nice thinking. Any idea how to cope
   > with that?
   >
   >
   [1]http://www.newmediacampaigns.com/page/browser-rest-http-accept-heade
   rs
   >
   > Cheers,
   >
   > /peter neubauer
   >
   > COO and Sales, Neo Technology
   >
   > GTalk: neubauer.peter
   > Skype peter.neubauer
   > Phone +46 704 106975
   > LinkedIn [2]http://www.linkedin.com/in/neubauer
   > Twitter [3]http://twitter.com/peterneubauer
   >
   > [4]http://www.neo4j.org - Your high performance graph database.
   > [5]http://nosqleu.com - The biggest NOSQL event. Ever.
   > [6]http://www.thoughtmade.com - Scandinavias coolest Bring-a-Thing
   party.
   >
   >
   > On Wed, Apr 21, 2010 at 12:11 PM, Mattias Persson
   > <matt...@neotechnology.com> 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
   >> 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 use content negotiation.
   >>>
   >>> Jim
   >>> _______________________________________________
   >>> Neo mailing list
   >>> User@lists.neo4j.org
   >>> [7]https://lists.neo4j.org/mailman/listinfo/user
   >>>
   >>
   >>
   >>
   >> --
   >> Mattias Persson, [matt...@neotechnology.com]
   >> Hacker, Neo Technology
   >> [8]www.neotechnology.com
   >> _______________________________________________
   >> Neo mailing list
   >> User@lists.neo4j.org
   >> [9]https://lists.neo4j.org/mailman/listinfo/user
   > _______________________________________________
   > Neo mailing list
   > User@lists.neo4j.org
   > [10]https://lists.neo4j.org/mailman/listinfo/user
   _______________________________________________
   Neo mailing list
   User@lists.neo4j.org
   [11]https://lists.neo4j.org/mailman/listinfo/user

References

   1. http://www.newmediacampaigns.com/page/browser-rest-http-accept-headers
   2. http://www.linkedin.com/in/neubauer
   3. http://twitter.com/peterneubauer
   4. http://www.neo4j.org/
   5. http://nosqleu.com/
   6. http://www.thoughtmade.com/
   7. https://lists.neo4j.org/mailman/listinfo/user
   8. http://www.neotechnology.com/
   9. https://lists.neo4j.org/mailman/listinfo/user
  10. https://lists.neo4j.org/mailman/listinfo/user
  11. https://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to