Malaysian user cannot connect through websockets?

[hullionhero]

I have a malaysian user who's connecting through websockets, but is being dropped within 20 seconds, same thing with xhr-multipart.

xhr-polling works however.

Is he someone who I should tell to use the xhr-polling fallback or is there something I can do to make websocket work for him?

[pyrostrex]

Weird. I'm malaysian and using only 54kbps and am building a download service which eating much of my server connection. but still, I don't have such problem.

[3rd-Eden]

20 seconds is the heartbeat timeout of the server, so there must be something preventing him from sending back a heartbeat response to the server.

[xpepermint]

Native WebSockets are not working.

Crome example:
var socket = new WebSocket('ws://localhost:8124');

I dont's see any requests on nodejs+socket.io server side. When testing with basic nodejs server I see requests and the WebSocket protocol seams ok. I believe this is a critical bug!

That's why none of other Android/iPhone libraries don't work with Socket.IO.

[3rd-Eden]

Do you have a websocket server running on 8124? because that is not a valid socket.io url
On Jun 15, 2011, at 4:01 PM, xpepermint wrote:

Native WebSockets are not working.

Crome example:
var socket = new WebSocket('ws://localhost:8124');

I dont's see any requests on nodejs+socket.io server side. When testing with basic nodejs server I see requests and the WebSocket protocol seams ok. I believe this is a critical bug!

That's why none of other Android/iPhone libraries don't work with Socket.IO.

Reply to this email directly or view it on GitHub:
https://github.com/LearnBoost/Socket.IO-node/issues/238#issuecomment-1373792

[xpepermint]

Hum... yes... I use 8124 and it works with socket.io-client library. I also tried port 80 (var socket = new WebSocket('ws://localhost');) and it still does not work.
Am I missing something?