Geek Answers Handbook

Alternative Push / Comet server implementation for Android browser without sending 4 KB messages?

I am developing a web application that uses the Comet Hidden iFrame technique to transfer data from a server to a mobile browser.

Everything works fine on Mobile Safari, but Android is much more painful. It seems that sending messages from the server requires sending 4 KB of messages. This is not only the first for each message.

Some people tried to inject a comet using XMLHttpRequest streaming, but have the same 4K problems (http://code.google.com/p/android/issues/detail?id=13044)

Has anyone been able to implement Comet methods in an Android browser without requiring 4KB to enter messages?

Tested on Android 2.1.2.2

The server dispatched the event does not seem to be supported even in Android 4.0 version http://caniuse.com/eventsource

Same thing for websocket http://caniuse.com/websockets

thank

-seb

+5
source share
3 answers

Not sure if it qualifies as an answer to your immediate problem, but the general recommendation is to use future proof technology that returns to a reasonably good polyfill .

, WebSockets - WebSocket (node.js, Kaazing) . Kaazing: ​​ , WebSocket, WebSocket. WebSocket , WebSocket.

+2

4 - , Android Internet.app( ).

, 4KB . , HTTP Streaming - , HTTP Long- . , , Long-Polling, , . , 4KB , ( ). -.

, Caplin Systems, HTTP , , , .

- Comet Android, 4KB?

, - . WebSockets ( @Peter Moskovits) - , ( ) -. Android , Flash, , - Flash fallback, , Android WebSockets.

+1

Android, rgd. WebSockets:

  • Firefox Mobile ( RFC6455)

  • the built-in browser does not support WS at all (up to Android 4),

  • Chrome for Mobile (full RFC6455) .. available only for Android 4

+1
source

More articles:


All Articles