-
Notifications
You must be signed in to change notification settings - Fork 439
Support for socket.IO 1.0 #162
Comments
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. |
ok, v1.0 landed, including some major changes that break the current version of the library. 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)... If you don't have time to support v1.0, I would like to check your work in progress branch. |
+1, socket.io v1.0 looks cool. |
I agree, support for socket.io 1.0 would be awesome 👍 |
+1, need support for v1.0 |
+1 |
@yosuke-furukawa no, not even the connection works anymore. |
@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: And the corresponding blog post: |
Support for socket.io 1.0.x #197 |
+1 - 1.0+ support would be great. It is much smoother than previous versions. |
+1 Also, @sweinertjr! Sup! |
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? |
Waiting for 1.0 support and also for swift support. 👍 |
@jklinson: Waiting for 1.0 support and also for swift support. 👍 |
It'll be really great to have support for 1.x. |
Socket 1.x support would be great.:+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 i would like to create static library with objective C as well, do you able to achieve it? |
@marcuschoong |
@b9AobJ |
@marcuschoong |
@b9AobJ |
@marcuschoong hi, i also need to create a static library using socket i.o, have you solve the problem? |
I haven't solve the problem.
…On Fri, Jul 13, 2018 at 7:12 PM, sai ***@***.***> wrote:
@marcuschoong <https://github.com/marcuschoong> hi, i also need to create
a static library using socket i.o, have you solve the problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#162 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZpNerwq57DtUYRfnwE6tUoWkT3darqaks5uGICpgaJpZM4Btvvj>
.
--
Best Regards,
Marcus
|
@tooolkit @marcuschoong or use
|
@b9AobJ thx, i had choose the cpp version ,but i'm not familiar with cpp ,i can contact the server and when emit i can receive data. but i don't know how to get the data . have no idea how to cast objc type like NSDictionary to cpp. thank you very much. |
@tooolkit sorry, i use this to create project is 2016/11,and i forget about this project that how to use,i think is very simple for you ,maybe you could try to learn his API |
@b9AobJ thx for your replay. you are so kind. i have solve the problem cast data between std::map and NSDictionary. thank you very much. but maybe socket.io-client-cpp cant use in a static library. so many problems even i create a new project and just use socket.io-client-cpp. i made a issue to them . thank you very much. |
npm automatically updates socket.io to version 1.0 now. and this library doesn't support new version, stalls at handshake.
The text was updated successfully, but these errors were encountered: