[
https://issues.apache.org/jira/browse/COUCHDB-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041677#comment-13041677
]
Jan Lehnardt commented on COUCHDB-986:
--------------------------------------
In addition, the link cites:
"Implementors should be aware that this specification is not stable.
Implementors who are not taking part in the discussions are likely to find the
specification changing out from under them in incompatible ways. Vendors
interested in implementing this specification before it eventually reaches the
Candidate Recommendation stage should join the aforementioned mailing lists and
take part in the discussions."
That's an even better reason for not yet committing this to trunk.
> 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: Benoit Chesneau
>
> 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
