We have sent a pull request to the qooxdoo.
As WebSockets have not been implemented the qooxdoo way with basic, fallback,
reconnection, pool, cache, data binding etc, we decided to start it.
Any suggestions on it would be appreciated.
Stefan
Hallo Stefan,
first of all, thank you very much. I didn’t have time to check out any details
but one questions came to my mind right away. Why did you decide to use a pull
request instead of a contribution? This topic seems to be so huge and self
contained, it could be easily a contribution as w
Hi Martin,
It is easy to keep it as a contribution if that is what you want.
We chose an enhancement bug as Script/Xhr/Jsonp communication are core
functionality and we believe websocket should be too.
We also used the qx.io namespace of the same reason.
We believed it might help you
...but
Cool ... (although I don't have an immediate application for that, but I
know somebody with a Qooxdoo project using web sockets).
I also understand the argument about core functionality. But putting it
there only helps if 1&1 has the necessary ressources to maintain it (or at
least to make sure up
