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
Ensure that sockets are terminated by the client rather than the server, wherever possible.
Also ensure that observable termination yields deterministic results upon graceful shutdown; e.g., the client termination notification on the server should indicate that the observable terminated, not that the client terminated or that either side was forcibly closed by the remote connection.
The text was updated successfully, but these errors were encountered:
A previous release has vastly improved socket shutdown so that it's graceful and yields the appropriate reason(s). Leaving this item open for now just as a reminder to do a deeper review at some point.
Ensure that sockets are terminated by the client rather than the server, wherever possible.
Also ensure that observable termination yields deterministic results upon graceful shutdown; e.g., the client termination notification on the server should indicate that the observable terminated, not that the client terminated or that either side was forcibly closed by the remote connection.
The text was updated successfully, but these errors were encountered: