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
Right now ws timeouts are set in nginx to an obnoxiously long time. Otherwise, after 60 seconds, if the WS doesn't send anything we get a frame header error, and the sockets have to reconnect - This happens on rates and messages.
Instead of that, should set rates to respond more frequently (or move to an API call that is on a timer or something), and should send empty keepalive messages on the chat ws
The text was updated successfully, but these errors were encountered:
Right now ws timeouts are set in nginx to an obnoxiously long time. Otherwise, after 60 seconds, if the WS doesn't send anything we get a frame header error, and the sockets have to reconnect - This happens on rates and messages.
Instead of that, should set rates to respond more frequently (or move to an API call that is on a timer or something), and should send empty keepalive messages on the chat ws
The text was updated successfully, but these errors were encountered: