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.
If you're looking for "streamed" data from CouchDB, you might checkout the _changes feed. There's also been some Comet work done in the past (I think). If you're looking for incoming "streamed" data, Max Ogden's put up some Pubsubhubbub stuff for CouchDB: http://github.com/maxogden/couchpubtato Do you have a specific use case you're trying to solve with WebSockets? On Tue, Nov 2, 2010 at 11:55 AM, Fedor Indutny <fedor.indu...@gmail.com>wrote: > 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 > > http://damienkatz.net/2010/08/whats_new_in_couchdb_10_securi.html > > > > they are implemented in recent versions of Opera, Safari and Firefox: > > > > > > > -- > Fedor Indutny >
