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? > > http://www.newmediacampaigns.com/page/browser-rest-http-accept-headers > > Cheers, > > /peter neubauer > > COO and Sales, Neo Technology > > GTalk: neubauer.peter > Skype peter.neubauer > Phone +46 704 106975 > LinkedIn http://www.linkedin.com/in/neubauer > Twitter http://twitter.com/peterneubauer > > http://www.neo4j.org - Your high performance graph database. > http://nosqleu.com - The biggest NOSQL event. Ever. > http://www.thoughtmade.com - Scandinavias coolest Bring-a-Thing party. > > > On Wed, Apr 21, 2010 at 12:11 PM, Mattias Persson > <[email protected]> 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 <[email protected]> >> >>> Just another thought: if we're going to use multiple representation >>> formats, then we should use content negotiation. >>> >>> Jim >>> _______________________________________________ >>> Neo mailing list >>> [email protected] >>> https://lists.neo4j.org/mailman/listinfo/user >>> >> >> >> >> -- >> Mattias Persson, [[email protected]] >> Hacker, Neo Technology >> www.neotechnology.com >> _______________________________________________ >> Neo mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
