[ 
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061718#comment-13061718
 ] 

Jason Smith commented on COUCHDB-1175:
--------------------------------------

I humbly submit that the problem remains insufficiently clearly-defined to 
negotiate the answer.

Top-of-my-head, some confounding factors, sorted randomly, by relevance.

* Browsers have built-in Accept defaults
* The jQuery that ships with Futon overrides these
* Future jQuery versions, or alternative AJAX libraries, which developers 
require override these
* Browsers and servers tend to become more standard over time, not less
* Couch tends to show us the future, not the past (cf. HTTP, REST, Erlang, 
Javascript, replication; "I was into Erlang before it was cool" as the man says)
* Wikipedia (body) and Google search (mind) have become self-aware (cf. the 
greatest film ever, "Ghost in the Shell"). This being has no corporeal form but 
is, in point of fact, omnipresent, omnipotent, and benevolent within 
cyberspace. Having a superior intellect, it was naturally drawn to CouchDB and 
made itself known to us by the name "Noah Slater." Cross swords with Noah 
Slater at your own peril.

For an unrelated problem, I need answers to some of these questions myself, so 
I will try to post concrete data during the weekend, either on the wiki as a 
table, or in here. My hope is that the answer will be more clear then.

> Improve content type negotiation for couchdb JSON responses
> -----------------------------------------------------------
>
>                 Key: COUCHDB-1175
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1175
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 1.0.2
>            Reporter: Robert Newson
>            Assignee: Robert Newson
>            Priority: Blocker
>             Fix For: 1.1.1, 1.2
>
>
> Currently we ignore qvalues when negotiation between 'application/json' and 
> 'text/plain' when returning JSON responses.
> Specifically, we test directly for 'application/json' or 'text/plain' in the 
> Accept header. Different branches have different bugs, though. Trunk returns 
> 'application/json' if 'application/json' is present at all, even if it's less 
> preferred than 'text/plain' when qvalues are accounted for.
> We should follow the standard.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to