danielniccoli
commented
11 years ago From rgl%ruil...@gtempaccount.com on October 29, 2008 16:31:30 Support for websocket is something that I would like to work on, but its also something that has no immediate use (web browsers will need to implement it too).
Something that I would like to do first, is to bring http://orbited.org (btw, I participate in that project) sockets style into cherokee (once this technology matures in orbited). Though, I'm not sure if you think its a good idea...
If you don't already known, orbited proxies data between the front-end browser and a backend TCP socket server (eg. LiveHelp [0] demo app allows you to access a normal IRC server using your browser); for doing that, it needs to buffer data inside orbited until the browser pick it up (similar to what a normal http reverse proxy does, I guess). Its something like this:
browser<--http-->orbited<--tcp-->backend_tcp_server
Inside the browser is some JS magic/glue [1] to make this work too.
Maybe you think this is to heavy lifting for cherokee and prefer this scheme:
browser<--http-->cherokee<--http-->orbited<--tcp-->backend_tcp_server
But for this to work, we need cherokee http reverse proxy (preferably with keep- alive too).
Though, having this built-in cherokee would allow us to drop the second http proxy connection (and maybe it would run a little faster because inside cherokee this would be implemented in C instead of python) and the orbited process.
[0] http://orbited.org/wiki/LiveHelp [1] http://orbited.org/wiki/TCPSocket
ghost
lkraav
skinkie
emiliocampos-zevenet
Original author: alobbs (October 29, 2008 08:57:46)
We ought to start thinking about adding HTML5 Websockets support:
http://www.whatwg.org/specs/web-apps/current-work/#network http://www.jroller.com/tedgoddard/entry/websocket_is_neither_web_nor
Original issue: http://code.google.com/p/cherokee/issues/detail?id=169