[
https://issues.apache.org/jira/browse/COUCHDB-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006566#comment-13006566
]
Paul Joseph Davis commented on COUCHDB-841:
-------------------------------------------
Not to be a negative nancy, but I'd be fairly suspect of actually providing
websocket support until browser vendors decide that its going to be an actual
spec. For instance, the caniuse report [1] is less than exciting. There's also
the security issue [2] that's been floating around and to my knowledge has not
been addressed by the spec yet. Not to mention there are similar competing
specs that do similar things [3].
[1] http://caniuse.com/#feat=websockets
[2] http://www.0xdeadbeef.com/weblog/2010/12/disabling-websockets-for-firefox-4/
[3] http://dev.w3.org/html5/eventsource/
> Support WebSockets in continuous changes feeds
> ----------------------------------------------
>
> Key: COUCHDB-841
> URL: https://issues.apache.org/jira/browse/COUCHDB-841
> Project: CouchDB
> Issue Type: New Feature
> Components: HTTP Interface
> Affects Versions: 1.0
> Reporter: Dirkjan Ochtman
>
> Just wanted to put this on the roadmap: it would be nice if continuous
> changes feeds (and maybe some other things in CouchDB, not sure) could
> support WebSockets. WebSockets are an emerging standard (there's no final
> spec yet) with implementations in both recent Chrome and Firefox (beta)
> releases that allows servers to push information to the browser without
> having to do polling (or longpolling).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
