[
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
