-
Notifications
You must be signed in to change notification settings - Fork 366
No polling? #154
Comments
The thing is, the polling is needed to call the handshake which will return a key (a session id) to use the websockets, and also supported transports (polling, websockets, ...). That's at least how Socket.io used to work, I don't know if it changed since then. Unless if you think you can determine the session-id or bypass it, you could do a PR to ignore the |
Hmm, the changes looks like there are too complex, I think this follows to a backwards-compatibly change... |
Not seeing why, as it should a sort of option / configuration (if config or option is not defined, keep the current behavior). Try it, and we'll mind it if we need to. :} (Sorry for the delay, totally forgot about that :D) |
Nice to know this is still maintained! No worries! |
I wouldn't call this maintained but I still have a look around once in a while. I stopped using Elephant 3 years ago (or something like that), using AMQP instead (see #135). :} |
Hi,
for a new project, I need to do a websocket connection, but polling has been disabled. How can I deal with this in this lib, since I need avoid calling
handshake()
...Any tip?
Jens
Btw: I'm sorry, but I do not have StackOverflow.
The text was updated successfully, but these errors were encountered: