Hi all
Am 29.12.13 09:56, schrieb Vicente J. Ruiz Jurado:
El 28/12/13 11:17, Yuri Z escribió:
Yeah, I also think that Socket.IO causes a lot of issues. Once WIAB
supported only web sockets, but then we added Socket.IO to allow more
browsers that don't support websockets to work with it. It happened about 3
years ago, and the only browser that supported websockets fully was Chrome.
The problem is - Socket.IO was abandoned by it's author (Tad Glines is
actually also WIAB committer but he is not active for long time). In fact
the author himself suggested we would move to Comet or something similar.
As for me - I think we can just drop support for long polling and flash
modes that Socket.IO provides and just use web sockets.
>From my point of view, socket.io java library is used as a fallback when
websocket is not supported by the browser or it's not available because
of proxies/firewalls block it, something very common unfortunately (see
WaveWebSocketClient.java line 111).
Also from my perception, saving issues are caused also because of our
file persistence implementation (I'm using websocket in my browsers, and
I'm suffering saving issues also from time to time).
It would be no problem, if you could save manualy. The main problem is,
that you edit a text, and you maybe not recognize, that the text is
unsaved. If you recognize it, you have maybe allready some minuts
unsaved work, but you don't know, when wave stopped saving. So if you
reload, it's every time a surprise where your work stucked. This is
realy nasty. I will install WireShark now, to make deeper investagations.
Returning to websocket, I did several efforts to try to find an
alternative to that socket.io gwt lib, and IMHO, the more interesting
lib is atmosphere.
https://github.com/Atmosphere/atmosphere
https://github.com/Atmosphere/atmosphere/wiki/Getting-Started-with-the-samples
Also as a possibility to remove our jetty dependency in the server side
and try to run wave in other servlet containers.
But I don't find a easy way to integrate atmosphere with our server
websocket, guice and auth code, but I'm keep studying it and trying it.
Well, everytime switching libraries is also not a solution. Every
library has weeknesses. So, you solve maybe one problem and implement
two new. I prefer to solve the problem in our code if possible, or
upstream bugfixes to the libraries.
Meanwhile, I'm doing a little maintenance over this socket.io java fork:
https://github.com/vjrj/Socket.IO-Java/commits/master
This project I found, and that's why I ask, if we should update socklet
io on wave.
Greetings Raphael
