You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Patrick Mueller (Created) (JIRA)" <ji...@apache.org> on 2011/11/29 18:37:39 UTC
[jira] [Created] (CB-84) Use socket.io for network communication
Use socket.io for network communication
----------------------------------------
Key: CB-84
URL: https://issues.apache.org/jira/browse/CB-84
Project: Apache Callback
Issue Type: New Feature
Components: weinre
Reporter: Patrick Mueller
Assignee: Patrick Mueller
>From https://github.com/phonegap/weinre/issues/5
*davejohnson opened this issue June 23, 2011*
This is particularly good if we can take advantage of native sockets on ios and / or there is a socket plugin for phonegap
*pmuellr commented June 23, 2011*
An open investigation item I have for socket.io is how they do their cross-site i/o. Not sure if they depend on CORS or can use some other mechanism. If they can support cross-site i/o for iOS 3.1.x, it would mean we could actually support iOS 3.1.x in weinre, which we can't today. Same with some older versions of webOS.
I think converting to socket.io would be relatively straight-forward, but I wasn't particularly happy with the Java server impls I saw floating around. At this point, moving to socket.io would also likely mean moving to node for the server piece at the same time.
*davejohnson commented June 23, 2011*
agreed. I think socket.io and node go hand in hand.
--
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
[jira] [Commented] (CB-84) Use socket.io for network communication
Posted by "Jordan Stout (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291177#comment-13291177 ]
Jordan Stout commented on CB-84:
--------------------------------
Huge +1 on this. HTML5 / JavaScript native mobile apps is the future.... amongst the future of the web... included is Node.js and Socket.io. There NEEDS to be some sort of cross mobile socket support. I've tested socket.io on iOS and it worked (real quick test).
> Use socket.io for network communication
> ----------------------------------------
>
> Key: CB-84
> URL: https://issues.apache.org/jira/browse/CB-84
> Project: Apache Cordova
> Issue Type: New Feature
> Components: weinre
> Reporter: Patrick Mueller
> Assignee: Patrick Mueller
>
> From https://github.com/phonegap/weinre/issues/5
> *davejohnson opened this issue June 23, 2011*
> This is particularly good if we can take advantage of native sockets on ios and / or there is a socket plugin for phonegap
> *pmuellr commented June 23, 2011*
> An open investigation item I have for socket.io is how they do their cross-site i/o. Not sure if they depend on CORS or can use some other mechanism. If they can support cross-site i/o for iOS 3.1.x, it would mean we could actually support iOS 3.1.x in weinre, which we can't today. Same with some older versions of webOS.
> I think converting to socket.io would be relatively straight-forward, but I wasn't particularly happy with the Java server impls I saw floating around. At this point, moving to socket.io would also likely mean moving to node for the server piece at the same time.
> *davejohnson commented June 23, 2011*
> agreed. I think socket.io and node go hand in hand.
--
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
[jira] [Commented] (CB-84) Use socket.io for network communication
Posted by "Patrick Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292829#comment-13292829 ]
Patrick Mueller commented on CB-84:
-----------------------------------
No, currently not using socket.io at all in weinre. I've used socket.io for some other projects, and am generally happy with it. First thing to do to get socket.io in the picture, was to port the server from Java to node, since (at the time, a while back), I wasn't all that happy with the shape of the Java version of socket.io.
It shouldn't be too hard to add the socket.io support in, the basic protocol used by the server and clients is one-way message queues.
> Use socket.io for network communication
> ----------------------------------------
>
> Key: CB-84
> URL: https://issues.apache.org/jira/browse/CB-84
> Project: Apache Cordova
> Issue Type: New Feature
> Components: weinre
> Reporter: Patrick Mueller
> Assignee: Patrick Mueller
>
> From https://github.com/phonegap/weinre/issues/5
> *davejohnson opened this issue June 23, 2011*
> This is particularly good if we can take advantage of native sockets on ios and / or there is a socket plugin for phonegap
> *pmuellr commented June 23, 2011*
> An open investigation item I have for socket.io is how they do their cross-site i/o. Not sure if they depend on CORS or can use some other mechanism. If they can support cross-site i/o for iOS 3.1.x, it would mean we could actually support iOS 3.1.x in weinre, which we can't today. Same with some older versions of webOS.
> I think converting to socket.io would be relatively straight-forward, but I wasn't particularly happy with the Java server impls I saw floating around. At this point, moving to socket.io would also likely mean moving to node for the server piece at the same time.
> *davejohnson commented June 23, 2011*
> agreed. I think socket.io and node go hand in hand.
--
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
[jira] [Commented] (CB-84) Use socket.io for network communication
Posted by "Patrick Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291184#comment-13291184 ]
Patrick Mueller commented on CB-84:
-----------------------------------
Is there some kind of issue with the current communication protocol weinre uses? Using socket.io just means we get to replace some weinre code with something someone else supports. Doesn't provide any other HUGE bells and whistles over the top of what weinre uses now though.
As far as I know.
> Use socket.io for network communication
> ----------------------------------------
>
> Key: CB-84
> URL: https://issues.apache.org/jira/browse/CB-84
> Project: Apache Cordova
> Issue Type: New Feature
> Components: weinre
> Reporter: Patrick Mueller
> Assignee: Patrick Mueller
>
> From https://github.com/phonegap/weinre/issues/5
> *davejohnson opened this issue June 23, 2011*
> This is particularly good if we can take advantage of native sockets on ios and / or there is a socket plugin for phonegap
> *pmuellr commented June 23, 2011*
> An open investigation item I have for socket.io is how they do their cross-site i/o. Not sure if they depend on CORS or can use some other mechanism. If they can support cross-site i/o for iOS 3.1.x, it would mean we could actually support iOS 3.1.x in weinre, which we can't today. Same with some older versions of webOS.
> I think converting to socket.io would be relatively straight-forward, but I wasn't particularly happy with the Java server impls I saw floating around. At this point, moving to socket.io would also likely mean moving to node for the server piece at the same time.
> *davejohnson commented June 23, 2011*
> agreed. I think socket.io and node go hand in hand.
--
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
[jira] [Commented] (CB-84) Use socket.io for network communication
Posted by "Patrick Mueller (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211003#comment-13211003 ]
Patrick Mueller commented on CB-84:
-----------------------------------
The current master branch no longer includes the code or build bits for the standalone Mac app. Doesn't mean it can't come back. But there are issues.
If you're interested in seeing a standalone Mac app again, [open a new issue here|https://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?pid=12312420&components=12316604&issuetype=5]. I'd like to keep the discussion in this issue to focus on socket.io usage.
> Use socket.io for network communication
> ----------------------------------------
>
> Key: CB-84
> URL: https://issues.apache.org/jira/browse/CB-84
> Project: Apache Callback
> Issue Type: New Feature
> Components: weinre
> Reporter: Patrick Mueller
> Assignee: Patrick Mueller
>
> From https://github.com/phonegap/weinre/issues/5
> *davejohnson opened this issue June 23, 2011*
> This is particularly good if we can take advantage of native sockets on ios and / or there is a socket plugin for phonegap
> *pmuellr commented June 23, 2011*
> An open investigation item I have for socket.io is how they do their cross-site i/o. Not sure if they depend on CORS or can use some other mechanism. If they can support cross-site i/o for iOS 3.1.x, it would mean we could actually support iOS 3.1.x in weinre, which we can't today. Same with some older versions of webOS.
> I think converting to socket.io would be relatively straight-forward, but I wasn't particularly happy with the Java server impls I saw floating around. At this point, moving to socket.io would also likely mean moving to node for the server piece at the same time.
> *davejohnson commented June 23, 2011*
> agreed. I think socket.io and node go hand in hand.
--
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
[jira] [Commented] (CB-84) Use socket.io for network communication
Posted by "Filip Maj (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292651#comment-13292651 ]
Filip Maj commented on CB-84:
-----------------------------
Pat, does the current communication protocol use WebSockets at all? socket.io would solve this (and would fall back to long-polling XHR when unavailable on a client). It would improve latency on mobile clients where websockets are supported (iOS, BlackBerry and webOS).
> Use socket.io for network communication
> ----------------------------------------
>
> Key: CB-84
> URL: https://issues.apache.org/jira/browse/CB-84
> Project: Apache Cordova
> Issue Type: New Feature
> Components: weinre
> Reporter: Patrick Mueller
> Assignee: Patrick Mueller
>
> From https://github.com/phonegap/weinre/issues/5
> *davejohnson opened this issue June 23, 2011*
> This is particularly good if we can take advantage of native sockets on ios and / or there is a socket plugin for phonegap
> *pmuellr commented June 23, 2011*
> An open investigation item I have for socket.io is how they do their cross-site i/o. Not sure if they depend on CORS or can use some other mechanism. If they can support cross-site i/o for iOS 3.1.x, it would mean we could actually support iOS 3.1.x in weinre, which we can't today. Same with some older versions of webOS.
> I think converting to socket.io would be relatively straight-forward, but I wasn't particularly happy with the Java server impls I saw floating around. At this point, moving to socket.io would also likely mean moving to node for the server piece at the same time.
> *davejohnson commented June 23, 2011*
> agreed. I think socket.io and node go hand in hand.
--
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
[jira] [Commented] (CB-84) Use socket.io for network communication
Posted by "Olivier Louvignes (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210993#comment-13210993 ]
Olivier Louvignes commented on CB-84:
-------------------------------------
Will this node/socket.io magic will still be available as a OSX standalone? Does not see trace of it in https://github.com/apache/incubator-cordova-weinre
> Use socket.io for network communication
> ----------------------------------------
>
> Key: CB-84
> URL: https://issues.apache.org/jira/browse/CB-84
> Project: Apache Callback
> Issue Type: New Feature
> Components: weinre
> Reporter: Patrick Mueller
> Assignee: Patrick Mueller
>
> From https://github.com/phonegap/weinre/issues/5
> *davejohnson opened this issue June 23, 2011*
> This is particularly good if we can take advantage of native sockets on ios and / or there is a socket plugin for phonegap
> *pmuellr commented June 23, 2011*
> An open investigation item I have for socket.io is how they do their cross-site i/o. Not sure if they depend on CORS or can use some other mechanism. If they can support cross-site i/o for iOS 3.1.x, it would mean we could actually support iOS 3.1.x in weinre, which we can't today. Same with some older versions of webOS.
> I think converting to socket.io would be relatively straight-forward, but I wasn't particularly happy with the Java server impls I saw floating around. At this point, moving to socket.io would also likely mean moving to node for the server piece at the same time.
> *davejohnson commented June 23, 2011*
> agreed. I think socket.io and node go hand in hand.
--
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