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
{{ message }}
This repository was archived by the owner on Aug 29, 2018. It is now read-only.
Hi I'm searching for a way to disable or restrict the failed request queue to 1.
So basically socket.io queue's failed requests when network connection is gone and resends those when connection resumes.
How can I stop this behaviour or restrict the maximum amount of requests?
The text was updated successfully, but these errors were encountered:
I found this SO answer to set the Socket.io max reconnection retries. Not sure if that is what you are looking for. You might have more luck finding an answer in the Socket.io channels or GitHub.
Nah that's the reconnection timings.
If the connection is lost and you still try to do stuff, the client will queue those requests and send them when reconnected.
I solved it by checking if there is any internet connection in all actions lol, but its a kinda crappy solution. I wish there was a way to stop this behaviour of socket.io
Primus does have a queueSize option, but I couldn't make Primus work with socket.io
Hi I'm searching for a way to disable or restrict the failed request queue to 1.
So basically socket.io queue's failed requests when network connection is gone and resends those when connection resumes.
How can I stop this behaviour or restrict the maximum amount of requests?
The text was updated successfully, but these errors were encountered: