incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Stout (JIRA)" <>
Subject [jira] [Commented] (CB-882) Cross mobile socket support
Date Thu, 07 Jun 2012 18:48:22 GMT


Jordan Stout commented on CB-882:

I've yet to dig into the core of cordova.  I just toyed with it a few days ago... so to answer
your question, I'm not sure.  But whichever protocol is best supported for the device.  I
already have a node.js / app and wanted to build a cross platform (mostly native)
mobile app for the two... or how linkedin does it (
they are soon going to opensource their socket codebase.  I'm assuming you can already communicate
back and forth from a server to WebSocket?  I'm not a genius on this topic.  Just
browsing the interwebs, I haven't found any clear way of doing cross (mobile) platform sockets.
WebSocket and seems to work in iOS, but I hear not Android?

Meaning, if each supported platform could be built into the cordova core as a WebSocket wrapper.

> Cross mobile socket support
> ---------------------------
>                 Key: CB-882
>                 URL:
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: Android, BlackBerry, CordovaJS, iOS
>            Reporter: Jordan Stout
>            Assignee: Joe Bowser
>              Labels: features, socket, sockets
> I tested the use of 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 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 servers (or any other service) natively without including the
client scripts?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message