You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to scale a socket.io process to multiple dynos on Heroku which doesn't offer sticky-session routing and wanted to get around this issue by using WebSockets as the only transport. Is there any way to do this with 1.1? Also curious if anyone has any information on what the downsides of doing this would be other than losing browser compatibility?
The text was updated successfully, but these errors were encountered:
Seems like this will still falllback to using other transports if the Websocket connection fails (or perhaps it tries to use other connection methods first)
@distracteddev it shouldn't be using any other transports when using {transports: ['websocket']}. Does something (like debug output) seem to indicate otherwise?
You should probably limit the transports to only the WebSocket transport on the server too, if your connections will work with them only.
I am trying to scale a socket.io process to multiple dynos on Heroku which doesn't offer sticky-session routing and wanted to get around this issue by using WebSockets as the only transport. Is there any way to do this with 1.1? Also curious if anyone has any information on what the downsides of doing this would be other than losing browser compatibility?
The text was updated successfully, but these errors were encountered: