Experience implementing socket.io-client without node.js?

Question

JavaScript

The choice fell on this library for the transport level of data exchange between the browser and the server.
If someone has experience of using the client library without node.js as a backend, tell us what problems there may be in finishing the server part!

Answer 1

In the worst case, you will get periodic requests. There is nothing terrible. The library is pretty smart and adapts itself to the technology, there are sockets, we use them, otherwise the requests are Ajax. Everything is as simple as ever. I don’t know how ruby ​​works with the server (you want to connect it with ruby?), but if it’s like php (php instance is restarted for each request), then this can be fraught with a low response time, although if your hardware is normal, then there is nothing to be afraid of .

Answer 2

If this is for rails, you can look at the option from railscasts.com/episodes/260-messaging-with-faye

Answer 3

There is also github.com/sockjs/sockjs-client . Hands do not reach to experiment, so I can not say anything about him. There is a server version for other languages.