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
Because WebSocket is mostly a long-running request, it is not easy to limit when it will end with a request timeout. It would make more sense to terminate the request when no messages are sent or received for a certain period of time.
The existing idle timeout handler operates at the connection level so a new scheduler that can perform at the WebSocket level is necessary.
The text was updated successfully, but these errors were encountered:
Because WebSocket is mostly a long-running request, it is not easy to limit when it will end with a request timeout. It would make more sense to terminate the request when no messages are sent or received for a certain period of time.
The existing idle timeout handler operates at the connection level so a new scheduler that can perform at the WebSocket level is necessary.
The text was updated successfully, but these errors were encountered: