[
https://issues.apache.org/jira/browse/COUCHDB-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shorin updated COUCHDB-1726:
--
Component/s: HTTP Interface
Support WebSockets
using mochiweb to handle the requests.
Support WebSockets
--
Key: COUCHDB-1726
URL: https://issues.apache.org/jira/browse/COUCHDB-1726
Project: CouchDB
Issue Type: Improvement
Reporter: Dave Cottlehuber
patch just merged back in; Lucas has been using
this for quite a while already I believe.
https://github.com/mochi/mochiweb/blob/websocket/examples/websocket/websocket.erl
[~benoitc] maybe you want to discuss a little how mochicow etc work in rcouch
for a comparison.
Support WebSockets
websockets in mochiweb atm, and short of unpick
RJ's changes that went into misultin[1], or using an interim shim like
mochicow[2] while couchdb migrates to cowboy[3], implementing websockets will
be a tricky piece of work.
Any takers?
[1]: https://github.com/ostinelli/misultin/blob/master/src
[mochiweb
patch|https://github.com/zotonic/zotonic/blob/master/modules/mod_base/controllers/controller_websocket.erl]
for websocket support. See the related [meeting
topic|http://www.mail-archive.com/dev@couchdb.apache.org/msg26563.html] about.
Support WebSockets in continuous changes feeds
WebSockets.
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
Dave Cottlehuber created COUCHDB-1726:
-
Summary: Support WebSockets
Key: COUCHDB-1726
URL: https://issues.apache.org/jira/browse/COUCHDB-1726
Project: CouchDB
Issue Type: Improvement
in rcouch as well.
Support WebSockets
--
Key: COUCHDB-1726
URL: https://issues.apache.org/jira/browse/COUCHDB-1726
Project: CouchDB
Issue Type: Improvement
Reporter: Dave Cottlehuber
[
https://issues.apache.org/jira/browse/COUCHDB-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau reassigned COUCHDB-1726:
Assignee: Benoit Chesneau
Support WebSockets
[
https://issues.apache.org/jira/browse/COUCHDB-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Cottlehuber updated COUCHDB-1726:
--
Labels: couchdb, erlang, gsoc2013, rest, (was: )
Support WebSockets
,)
Support WebSockets
--
Key: COUCHDB-1726
URL: https://issues.apache.org/jira/browse/COUCHDB-1726
Project: CouchDB
Issue Type: Improvement
Reporter: Dave Cottlehuber
Assignee: Benoit Chesneau
[
https://issues.apache.org/jira/browse/COUCHDB-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-1726:
-
Labels: couchdb erlang (was: couchdb erlang gsoc2013)
Support WebSockets
At the first I tough what a crazy idea but then ...
Why use the WebSockets only for notification with _changes feed. Why not use
the WS for realtime like streaming replication?
It is fast and bidirectional and could furthermore be speedup by streaming in a
binary format.
Or was my first
of longpoll plus the long-lived connection
benefits of continuous feed types. The EventSource standard, while still a
working draft too, has a bit more mature browser support than WebSockets:
http://caniuse.com/#feat=eventsource
Support WebSockets in continuous changes feeds
this in favor of #986.
Support WebSockets in continuous changes feeds
--
Key: COUCHDB-841
URL: https://issues.apache.org/jira/browse/COUCHDB-841
Project: CouchDB
Issue Type: New
be nice, but Server Sent Events
(SSE) is better suited for the _changes feed. This task is over a year old with
no movement. Implementing SSE in couchdb would be very easy. I moved my vote
to the #986 task; I suggest others do the same.
Support WebSockets in continuous
this!
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
break?
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
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
this probably hasn't exactly arrived yet; it would
make more sense to wait until the protocol has been finalized. Which as far as
I gather should be close except for the security issue in the recent version.
On the other hand, I think the caniuse-report is looking rather promising, with
websockets
. Let's do it!
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
+1 on websockets a better fit. The exact fit ;)
After all, it can go very nice with erlang messaging concept.
http://armstrongonsoftware.blogspot.com/2009/12/comet-is-dead-long-live-websockets.html
On 2 November 2010 21:22, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Tue, Nov 2, 2010 at 19:32
is there a websockets interface in development?
regards
Jonathan Chetwynd
www.peepo.com
notwithstanding: WebSockets are not even a fixed standard so far
http://damienkatz.net/2010/08/whats_new_in_couchdb_10_securi.html
they are implemented in recent versions of Opera, Safari and Firefox:
As I know, websockets wouldn't be implemented in couchdb, while it's a
draft.
2010/11/2 jonathan chetwynd j.chetw...@btconnect.com
is there a websockets interface in development?
regards
Jonathan Chetwynd
www.peepo.com
notwithstanding: WebSockets are not even a fixed standard so far
The draft status isn't what would keep WebSockets out of CouchDB. CouchDB
uses HTTP for it's API, so unless CouchDB were to pipe HTTP over the
WebSocket protocol (which would be silly) or implement a straight
TCP/IP-based API (which is highly unlikely), WebSockets doesn't bring much
to the table
On Tue, Nov 2, 2010 at 19:03, Benjamin Young benja...@couchone.com wrote:
The draft status isn't what would keep WebSockets out of CouchDB. CouchDB
uses HTTP for it's API, so unless CouchDB were to pipe HTTP over the
WebSocket protocol (which would be silly) or implement a straight
TCP/IP
On 2 Nov 2010, at 19:07, Dirkjan Ochtman wrote:
On Tue, Nov 2, 2010 at 19:03, Benjamin Young benja...@couchone.com wrote:
The draft status isn't what would keep WebSockets out of CouchDB. CouchDB
uses HTTP for it's API, so unless CouchDB were to pipe HTTP over the
WebSocket protocol (which
[
https://issues.apache.org/jira/browse/COUCHDB-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis updated COUCHDB-841:
--
Skill Level: Regular Contributors Level (Easy to Medium)
Support WebSockets
for his own use cases).
As for final spec, I'm not sure there'll be something like a version 1.0, but
there'll be a working draft or something that has reached consensus and is
implemented in the same way in several different browsers (likely Gecko and
Webkit).
Support WebSockets in continuous
? 1.0?
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
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
31 matches
Mail list logo
