thanks for your feedback. You might be interested in this thread which
talks about keeping the radio in HSPA DCH state on 3.5G networks:
Keeping a WebSocket connections "snappy" on mobile networks is tricky.
IMO, an API is clearly missing that would allow apps to control the
tradeoff between power and bandwidth/latency (allocated channels and
radio state). The carrier view might be different on that of course;)
Regarding your code: could you clone our repo on GitHub and apply your
changes there? That would make it much simpler so see diffs and probably
Am 01.08.2012 22:01, schrieb patrickbrown:
I am using websockets on an android device and I am finding bad
behavoiur and slowness when a roam occurrs.
I think I have resolved this by reducing connection tineouts,disabling
nagle, and some other socket options
Here is the code change.
Also tracking purposes would you be amenable to keep statistics of the
That is counters would be added in the software to track behaviour and a
method that would then present these statistics to the caller.