Hi Yuri
Am 28.12.13 11:17, schrieb Yuri Z:
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.
Well, if the project is abdoned, the easyest solution is maybe to
reintegrate Websocklet, and use a browser switch to decide if we provide
Websocklet or socklet.io. Would it be hard to do this?
Greetings Raphael
On Sat, Dec 28, 2013 at 10:06 AM, Raphael Bircher <r.birc...@gmx.ch> wrote:
Hi all
Ok, by closer investegation, I have now a suspect for this error. Socked
io. Has someone any info how old our socked io is? Maybe it needs a update.
Greetings Raphael
Am 28.12.13 00:12, schrieb Raphael Bircher:
Hi at all
I test at the moment WIAB more intensive. I notice that sometimes WIAB
dosn't save. This is nasty, because, you don't have the chance to force
WIAB to save. The only way I see, is to refresh, but then you loos your
text.
At the moment I could not isolate the problem. I was on the same Wave
with a older Safari, who has some crazy trubble with the editing. It looks
like JavaScript problems for me. I will now continue editing my text
without watching the edits from this computer. Just to see if the problem
strikes again.
Greetings Raphael
