Marek
SockJS-erlang fails on slow websocket consumer. For example: ``` =ERROR REPORT==== 26-Nov-2012::14:20:55 === ** Handler sockjs_cowboy_handler terminating in websocket_handle/3 for the reason exit:{noproc, {gen_server,call, [,{received,[]},infinity]}} ** Message was {text,} **...
Running out of atoms may kill the VM.
As discussed here: ``` https://groups.google.com/d/msg/sockjs/vsFvHqppq5g/XQPgErs9BpUJ ``` We should introduce three new calls: ``` sockjs:send_multi([Conn], iolist) sockjs:prepare(iolist) Conn:send_prepared(prepared) ``` Of course `send_multi` might use `prepared` underneath.
Max suggests that we could use hibernate to save memory: http://groups.google.com/group/sockjs/msg/152fc7a4c0718657
To fulfill sockjs/sockjs-client#67 we need to rename option `heartbeat_delay` to `server_heartbeat_interval`.
Related: mrjoes/sockjs-tornado#32
Some websocket implementations can't receive/send binary data over websockets yet: https://bugzilla.mozilla.org/show_bug.cgi?id=666349 We also need to make that working over fallback protocols.
To prevent clickjacking new browsers introduced `X-Frame-Options` header. Although SockJS does not have any clickable elements, it would be good to send this header for hygiene. Especially for pages that...
Twice in the tests we use POST_async with load set to False. This is racy. We should change the protocol to always send headers immediately, also on XHR-polling. This requires...
Heartbeats are not tested now. They should be.