You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Olivier Louvignes (Commented) (JIRA)" <ji...@apache.org> on 2012/02/18 16:42:59 UTC

[jira] [Commented] (CB-84) Use socket.io for network communication

    [ 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