announce "this project is not maintained anymore"

[mattqs]

THIS PROJECT IS DEPRECATED
Component is not maintained anymore.

I use this library in my own project. The last version that works with my project is 1.0.2.

[cmuentes]

Was this project just recently deprecated? It appears this issue was just opened and I just recently started using it on my project

[mattqs]

Looking for someone who has the resources to write/maintain an alternative.
#70

[mattqs]

New Socket.IO Client!
#71

https://github.com/IBM/socket-io

[PranKe01]

Is there any alternative? The IBM implementation does not support client certificates :| Is there any way to use socket.IO in .Net (C# or C++) with client side certificates? :|

[xzycn]

@PranKe01
Maybe this one pointed out in official README.

[PranKe01]

@PranKe01
Maybe this one pointed out in official README.

No, it does not has certificate support :|

[Archtica]

I know this is being deprecated, but I really enjoy using for it many projects.
I have one issue with connecting to a namespaces. I'm connecting to a very simple node server and namespaces works from other clients, but not from this.
My code is:

IO.Options op = new IO.Options { ForceNew = true, AutoConnect = false, Reconnection = false, ReconnectionDelay = 500, ReconnectionAttempts = 3, Secure = false, Upgrade = true }; Uri uri = new Uri(address); Manager manager = new Manager(uri, op); socket = manager.Socket("/example"); socket.Open();

It connects to root but is never lifted to the specified namespace. I tried everything for two days. Is this is a know bug then I'll stop trying

[pranathlcp]

@kissworks ,

Did you find a solution for this particular issue?

[cvaldezUM]

@kissworks @pranathlcp
Use Socket.IO server version 1.7.4.
Any version below 2 should work.

  "dependencies": {
    "socket.io": "1.7.4"
  }