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
If Close() is fired before Connect() completes it may be possible to end up with a dangling open connection. Probably need isConnecting and/or isOpening states to handle situations such as this, along with deferred execution (ie if Close() is called while isConnecting then defer the close action until connect() has completed).
The text was updated successfully, but these errors were encountered:
Currently, close is not allowed to be called until the port is open (which does happen immediately upon connect actually, given promises are specified to be run synchronously. This seems like an implementation detail at the moment though?).
Ideally we should be able to close before connect has completed in a clear manner (such that connectQueue would be cleared, and perhaps the other party notified).
If Close() is fired before Connect() completes it may be possible to end up with a dangling open connection. Probably need isConnecting and/or isOpening states to handle situations such as this, along with deferred execution (ie if Close() is called while isConnecting then defer the close action until connect() has completed).
The text was updated successfully, but these errors were encountered: