Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently WebSocketResponse "swallows" the exception at
and In
There is nothing that can be done if exception happens when a push message is broadcasted.
Can this be improved somehow? Now that we are asynchronous sending maybe we can "recover" from this case? This is failing in our app and server state gets "disconnected" from client state.