couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Young (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-1281) Implement Accept header based content negotiation for the _changes feed
Date Wed, 14 Sep 2011 12:15:09 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Young updated COUCHDB-1281:
------------------------------------

    Description: 
Current "continuous" and "longpoll" (and potentially text/event-stream feeds; see COUCHDB-986)
are selectable only via a "feed" query parameter. Ideally, it would be best for these feed
types to be made available based on Accept headers sent with the request. Browsers and "lesser"
HTTP clients who don't offer header alteration or addition could fall back to the current
"feed" query param as needed.

This addition would allow clients to send "Accept: text/event-stream" (or other mimetypes)
with a _changes feed request and receive the stream body in that mimetype. The current "continuous"
and "longpoll" responses would need their own registered mimetypes (rather than just text/plain
or application/json). These mimetypes could still be used in conjunction with the "feed" query
param.

  was:
Current "continuous" and "longpoll" (and potentially text/event-stream feeds; see #COUCHDB-986)
are selectable only via a "feed" query parameter. Ideally, it would be best for these feed
types to be made available based on Accept headers sent with the request. Browsers and "lesser"
HTTP clients who don't offer header alteration or addition could fall back to the current
"feed" query param as needed.

This addition would allow clients to send "Accept: text/event-stream" (or other mimetypes)
with a _changes feed request and receive the stream body in that mimetype. The current "continuous"
and "longpoll" responses would need their own registered mimetypes (rather than just text/plain
or application/json). These mimetypes could still be used in conjunction with the "feed" query
param.


> Implement Accept header based content negotiation for the _changes feed
> -----------------------------------------------------------------------
>
>                 Key: COUCHDB-1281
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1281
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>            Reporter: Benjamin Young
>              Labels: api, http, httpmime, rest, restful
>
> Current "continuous" and "longpoll" (and potentially text/event-stream feeds; see COUCHDB-986)
are selectable only via a "feed" query parameter. Ideally, it would be best for these feed
types to be made available based on Accept headers sent with the request. Browsers and "lesser"
HTTP clients who don't offer header alteration or addition could fall back to the current
"feed" query param as needed.
> This addition would allow clients to send "Accept: text/event-stream" (or other mimetypes)
with a _changes feed request and receive the stream body in that mimetype. The current "continuous"
and "longpoll" responses would need their own registered mimetypes (rather than just text/plain
or application/json). These mimetypes could still be used in conjunction with the "feed" query
param.

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

        

Mime
View raw message