incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-84) Use socket.io for network communication
Date Mon, 11 Jun 2012 15:14:43 GMT

    [ 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

        

Mime
View raw message