The question is about the default browser.
The server receives the message, processes it and responds back to the client with a success or error code. Finally, the connection is closed. For each request or say for 100 requests a new connection or 100 new connections are established and then closed. WebSocket is a bidirectional protocol.
WebSocket, as an IETF standard, and with a W3C browser API, is fully supported by all modern browsers: Chrome 16 + (incl. Chrome for Android)
Websockets can be used by any client (read: "app"), as long as the client implements the Websocket protocol - no browser (or hybrid) required.
The WebSocket API is an advanced technology that makes it possible to open a two-way interactive communication session between the user's browser and a server. With this API, you can send messages to a server and receive event-driven responses without having to poll the server for a reply.
Android 3.0 highlights doesn't mention anything about websockets.
Running the browser in a 3.0 AVD and going to websocket.org - echo test shows:
If I go to caniuse.com - websockets in mobile and desktop browsers, the page shows "Not supported" for Android 2.1 - 2.3.
Firefox Mobile 8 (https://wiki.mozilla.org/Mobile/Platforms/Android#Download_Aurora) supports WebSockets protocol version 8, draft version 10. It generally behaves exactly as the desktop version. WS works like a charm.
Only android 4.4 kitkat factory default browsers officially support websockets so you can NOT assume that a random device less than android 4.4 has a factory default browser that can support web-sockets As a result when you develop applications using web-view you have to take this in to account. That's why for example in Cordova you may need this plugin to ensure that your web-socket enabled application works in android versions less that 4.4
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With