[ 
https://issues.apache.org/jira/browse/CB-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291211#comment-13291211
 ] 

Patrick Mueller commented on CB-882:
------------------------------------

If there's something in the Cordova android platform preventing socket.io from 
working, and it's something we can "fix", I'd like to see that - as a separate 
issue of course.

I've not been keeping up-to-date with socket.io and WebSocket enough to know 
often they are changing, etc.

Is the current version of WebSocket going to be around for a while?  Is 
everyone implementing to it?  I think Safari and Chrome are shipping different 
protocol implementations for WebSocket, right now, for instance.  I'd want to 
wait till the spec is pretty well "cooked" before investing in supporting this.

And it should probably be prototyped as a separate plugin for now anyway.  At 
https://github.com/phonegap/phonegap-plugins or elsewhere, before being 
considered becoming part of the base.
                
> Cross mobile socket support
> ---------------------------
>
>                 Key: CB-882
>                 URL: https://issues.apache.org/jira/browse/CB-882
>             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 socket.io 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 socket.io 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 socket.io servers (or any other service) natively 
> without including the socket.io client scripts?

--
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

        

Reply via email to