socket.IO-objc
socket.IO-objc copied to clipboard
pkyeck
Support for socket.IO 1.0
npm automatically updates socket.io to version 1.0 now. and this library doesn't support new version, stalls at handshake.
socket.io v1.0 isn't final yet but I'll take a look at this. thanks for the heads up.
when fetching the current version from NPM, I still get the 0.9.16.
https://www.npmjs.org/package/socket.io
ok, v1.0 landed, including some major changes that break the current version of the library. I don't have the time right now to implement the new protocol ... but maybe someone other than me wants to try ...
I did take a look at v1.0 back in march and started to adjust the library but couldn't finish it - will check in the "work in progress" to a dedicated branch. maybe someone can use this as a starting point.
come august I'll have some spare time at my hands ...
Can we connect socket.io [email protected] using master brunch?
I need not to use new features (like binary support), however, socket.io v0.9.16 has problems (like memory leaks)... SO we would like to upgrade socket.io servers to v1.0.
If you don't have time to support v1.0, I would like to check your work in progress branch.
@yosuke-furukawa no, not even the connection works anymore. @all others please stop +1-ing - I know that this would be great but I don't have the time right now. keep you updated when this changes ...
@pkyeck The people +1'ing are not pressuring you to do it, they are just expressing the need for an update. Developers looking to do something worthwhile might pick up on it and start committing new code.
I've tried to implement just the Handshake Url's but didnt work well.. Hope you got some time to work it out @pkyeck
We are thousands to hope for it, but it seems that few of us are able to get it done...
+1 - 1.0+ support would be great. It is much smoother than previous versions.
It seems that they've offloaded the transports and browser incompatibilities into a separate module.
Here's a link to the new protocol definition: https://github.com/automattic/engine.io-protocol
And the corresponding blog post: http://socket.io/blog/introducing-socket-io-1-0/#new-engine
+1 - 1.0+ support would be great. It is much smoother than previous versions.
I also would love to see 1.0+ support. Thanks for your work, @pkyeck!
Does anyone know if it’s possible / easy to port everything to swift, so that it’s not necessary to use the Obj-C bridge?
@jklinson: Waiting for 1.0 support and also for swift support. :+1: Me too :+1:
I forked francoistemasys's great fork (it provides some socketio1.0 support) to add ack callback support to it(txt only, not binary). In the process I broke some 0.9 support (see comment in socketiopacket.m easy to fix)
https://github.com/francoisp/socket.IO-objc
Also, I just came accross this, linked on the socketio's ws but not ranking v high with google, it might be of interest if 0.9 support is not required: https://github.com/MegaBits/SIOSocket
@francoisp thanks for the link - he uses a javascript-bridge for the "native" implementation - clever ;) so there are multiple libraries that support 1.0. not fully right now but growing in scope. happy to see this. I'll link to your fork and the other link in the readme.
@pkyeck Just for knowledge , do you think you will have time to create library support for v1.0 ?
@Tejas-narola no, sadly not. but as I said before, if someone wants to contribute - be my guest
Looks that there is now a native implementation of the client for 1.0: https://github.com/socketio/socket.io-client-swift
thx for @francoisp ,it fix my demand,i want to create static library with use oc,if i use socket.io-client-swift to dynamic library,it will increase 70M+ libSwiftBridge.framework to my project😂
@b9AobJ I'm using https://github.com/francoisp/socket.IO-objc and tried to connect to my socket server but couldn't connect. following is the log file.
2018-04-12 15:29:31.518 SocketTesterARC[98538:14802812] Connecting to socket with URL: http://2cad7a38-ff.zzz.info/socket.io/1/?EIO=2&transport=polling&t=1523518171516&role=visitor 2018-04-12 15:29:31.703 SocketTesterARC[98538:14802812] didReceiveResponse() 200 2018-04-12 15:29:35.076 SocketTesterARC[98538:14802812] connectionDidFinishLoading() 2018-04-12 15:29:35.082 SocketTesterARC[98538:14802812] VERSION 10x 2018-04-12 15:29:35.082 SocketTesterARC[98538:14802812] Response {"sid":"ive1ab-NpEVYlpdBAAAT","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000} 2018-04-12 15:29:35.082 SocketTesterARC[98538:14802812] websocket supported -> using it now 2018-04-12 15:29:35.082 SocketTesterARC[98538:14802812] Received All information: sid: ive1ab-NpEVYlpdBAAAT heartbeat: 25.000000 Transport: <SocketIOTransportWebsocket: 0x7b90a580> 2018-04-12 15:29:38.436 SocketTesterARC[98538:14802812] start/reset Heartbeat 2018-04-12 15:29:38.437 SocketTesterARC[98538:14802812] Prepare to send() 2018-04-12 15:29:38.437 SocketTesterARC[98538:14802812] queue >>> 2probe 2018-04-12 15:29:42.761 SocketTesterARC[98538:14802812] onDisconnect() 2018-04-12 15:29:44.823 SocketTesterARC[98538:14802812] socket.io disconnected. did error occur? Error Domain=org.lolrus.SocketRocket Code=2132 "received bad response code from server 400" UserInfo={NSLocalizedDescription=received bad response code from server 400}
i would like to create static library with objective C as well, do you able to achieve it?
@marcuschoong I give up use this pr,and use this cpp project into my workspace, https://github.com/socketio/socket.io-client-cpp