Websocket in Android chrome (client) is failing when server sends message too fast.

[Von]

When I'm using chrome on desktop it works well although I'm still resorting on adding Sleep (30) on the server just right after every send. If I don't do this the chrome on desktop would also fail.

On android chrome the 30ms sleep seems not enough I tried increasing it upto 100ms but there's a noticieable stutter. Also I'd rather not use Sleep. What seems to be the problem? 

If its relevant TCP_NODELAY is enabled on the server. 

Thanks!

[PhistucK]

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.