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 19:04:23 GMT


Jordan Stout commented on CB-882:

Yeah that makes sense as a "plugin" also.  But the plugin repository seems to be anyone who
built something, it gets accepted.  Meaning, I'd like to start seeing plugins that work for
multiple browsers (such as the ones in the cordova core... (Media/Camera/etc))....

Since we have the list of what works for using native html5 websockets, and android doesn't
support it, can be wrapped...
Maybe HTML5 sockets is slow on a certain device and they have native tools available already,
we can use those.

Just some ideas I was wondering about.

Love the work btw.... I'm new and hope to start contributing once I dig deeper.  I just liked
that I deployed an html5 socket app in about 5 minutes to my iPhone :)... I was basically
controlling my radio from my phone =) Fun coding!
> 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