The key here is that the *URI* is the determining factor on the type of representation (compact or not), and clearly the client, who will request a specific URI, is aware of which type of request has been made.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jim Webber Sent: Sunday, May 22, 2011 11:12 AM To: Neo4j user discussions Subject: Re: [Neo4j] Compact JSON format for the server Hi Peter, > How does then the "compact" parameter work in other Accept headers than > "application/json" work? I think Ian's saying it's not to be used in the Accept header. He's saying identify the *variant* through a different URI. > Since this is a representation that compacts in > JSON, maybe the subformat is ok anyway? No, I don't think it is. It is JSON - that's how it should be processed. I think it's wrong to overload media types in this way. > Otherwise, how do we then name that return-format parameter so it doesn't > get mixed up with other, "normal" paramters? It's JSON. Just like our "normal" stuff is JSON. The only processing directive we give is application/json and that's true whichever variant is returned. If you are a client of Neo4j then you must be prepared to accept either of our JSON responses (or HTML or whatever). The same is also true if you abuse the media type - it's just that you've pretended one kind of response is different. Jim _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
