
Actually, we have been looking towards sock.js, which already has multiple
language implementations. A Yesod user that works with node.js also said he
tried both and thought sock.js was better.
http://www.rabbitmq.com/blog/2011/09/13/sockjs-websocket-emulation/
On Fri, Nov 4, 2011 at 9:32 AM, yi huang
On Fri, Nov 4, 2011 at 9:22 PM, Greg Weber
wrote: Does client-side mean Haskell? I tend to think of websockets just as useful from a browser client.
I guess the future is something like socket.io ?
On Fri, Nov 4, 2011 at 2:00 AM, Jasper Van der Jeugt
wrote: Hello all,
I'm pleased to announce the release of websockets [1] 0.4.0.0 today. You can grab it on Hackage [2].
This update brings an (almost completely rewritten) library which has support for multiple versions of the protocol, meaning you can choose to write backwards-compatible applications, or use the latest and greatest, all using a common API.
All feedback is obviously welcome, I'd be glad to hear what you guys think. For the next version, client-side support is planned, so the library user can write clients in addition to servers. If there's any other feature you would like to see, feel free to let me know.
[1]: http://jaspervdj.be/websockets/ [2]: http://hackage.haskell.org/package/websockets
Cheers, Jasper
_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel
_______________________________________________ web-devel mailing list web-devel@haskell.org http://www.haskell.org/mailman/listinfo/web-devel