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
Currently both Channel and Connection make no distinction between server or client closure when emitting close event, which is desirable in certain cases, e.g. cleanup after close. But there are certain use cases that the user might need to know which peer first sent the close request. In these cases we need to make it clear whether it was server (by an error or forced stopping), or it was the client.
The text was updated successfully, but these errors were encountered:
Currently both
Channel
andConnection
make no distinction between server or client closure when emittingclose
event, which is desirable in certain cases, e.g. cleanup after close. But there are certain use cases that the user might need to know which peer first sent the close request. In these cases we need to make it clear whether it was server (by an error or forced stopping), or it was the client.The text was updated successfully, but these errors were encountered: