realtime updates and mobile browsers

[nzjrs]

Hi,

The support for mobile browsers seems patchy. WRT the demo app

Chrome on Android 4 -> everything tested works
Built in browser Android 4 -> real-time updates don't work
Built in browser Android 2.3.5 -> hangs on load

Would you consider implementing a fallback, polling, strategy for older browsers?

John

[petecorreia]

Yeah, currently it's using raw websockets which means older browsers won't get realtime updates.
I'll try to fix the Android problem, if you can fix it and submit a pull request, that would be awesome.

About the fallbacks, I'm thinking of creating them as add-ons to the library to keep it lightweight for those who don't want them. Ideally in the future there would be a build page where one would select which fallbacks to include when downloading.

What do you think?

[bjpirt]

I think the best way to handle fallbacks would be for Cosm to support something like SockJS, which is something we'd quite like to do so people can use the websocket functionality on more browsers.
Let me look into whether we can do that any time soon.
Ben

On 27 Nov 2012, at 11:05, Pete Correia notifications@github.com wrote:

Yeah, currently it's using raw websockets which means older browsers won't get realtime updates.
I'll try to fix the Android problem, if you can fix it and submit a pull request, that would be awesome.

About the fallbacks, I'm thinking of creating them as add-ons to the library to keep it lightweight for those who don't want them. Ideally in the future there would be a build page where one would select which fallbacks to include when downloading.

What do you think?

—
Reply to this email directly or view it on GitHub.