[
https://issues.apache.org/jira/browse/CB-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-882:
-------------------------
Component/s: (was: BlackBerry)
(was: iOS)
WP7
Bada
BlackBerry 6+ and iOS 4.2+ (I believe?) has websockets built into the webview
and thus exists in Cordova.
To clarify: the client-side socket.io script will "fall back" to long-polling
XHR to provide a websocket polyfill. Using socket.io on Android, Bada or WP7
(the Cordova platforms that do not have websockets natively in the webview)
essentially gives you a slower websockets API. Using socket.io on iOS, BB and
webOS, it will take advantage of the available websockets under the hood.
On Android, a contributor did work to support websockets on a very old (15
months!) branch, which actually [still
exists|https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-android.git;a=shortlog;h=refs/heads/WebSockets].
This work was abandoned due to the spec it was based on being deemed "unsafe"
in an RFC, but I believe that has now been cleared up.
No idea about Bada.
As for Windows Phone 7, no "native" support for it, however there is a [full
implementation available|http://websocket4net.codeplex.com] which also happens
to be Apache licensed. One potential avenue for introducing that.
I think championing for this change on the cordova mailing list (see cordova.io
for details) would be a good start. Jordan, for starting points on how to help
out, you could try your hand at rebasing/merging the Android branch of
websockets with the latest code and adding necessary polyfills to cordova-js.
> Cross mobile socket support
> ---------------------------
>
> Key: CB-882
> URL: https://issues.apache.org/jira/browse/CB-882
> Project: Apache Cordova
> Issue Type: New Feature
> Components: Android, Bada, CordovaJS, WP7
> Reporter: Jordan Stout
> Assignee: Joe Bowser
> Labels: features, socket, sockets
>
> I tested the use of socket.io in an iOS app and I was able to successfully
> communicate back and forth from mobile to desktop. All I did was grab the
> same socket.io script hosted from the node.js server (as a quick test)... Of
> course, this may be cool and all, but I'm not sure how "cross mobile" it is.
> How hard will it be to create native socket support for most (or all) devices
> so developers can talk to socket.io servers (or any other service) natively
> without including the socket.io client scripts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
