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] [Commented] (COUCHDB-986) EventSource feed type for _changes
Date Tue, 13 Sep 2011 20:59:09 GMT

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

Benjamin Young commented on COUCHDB-986:
----------------------------------------

Personally, I'd prefer to see the "feed" query parameter dropped entirely and have the selection
of the feed switch to an Accept header-based (i.e., content negotiation-based) approached.
That would allow us to respond correctly to requests for the new text/event-stream content
type. A wider ranging change of this kind would of course warrant its own ticket.

At any rate, using the temporary "experimental-eventsource" thing is fine as long as we support
both during the transition to the "eventsource" final option.

> EventSource feed type for _changes
> ----------------------------------
>
>                 Key: COUCHDB-986
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-986
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: HTTP Interface
>    Affects Versions: 1.0.1
>            Reporter: Fedor Indutny
>            Assignee: Jan Lehnardt
>         Attachments: 0001-trunk-eventsource-changes-feed.patch
>
>
> I'll implement EventSource protocol feed for _changes API (feed="eventsource").
> Some info about it: http://dev.w3.org/html5/eventsource/
> It's more useful than websocket, beacause it's read-only.

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

        

Mime
View raw message