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
When authentication fails, we send an auth failure back to the client. However, we essentially then wait for the client to disconnect. We would like to shut down the client actor as soon as we know the auth failure has been sent out. This is challenging because we don't actually know when that message is sent.
It seems like we need a way to know when a message has been sent to the connection actor from the protocol actor. Potentially using a future or something. This way we could take an action after we know the message has been sent.
The text was updated successfully, but these errors were encountered:
When authentication fails, we send an auth failure back to the client. However, we essentially then wait for the client to disconnect. We would like to shut down the client actor as soon as we know the auth failure has been sent out. This is challenging because we don't actually know when that message is sent.
It seems like we need a way to know when a message has been sent to the connection actor from the protocol actor. Potentially using a future or something. This way we could take an action after we know the message has been sent.
The text was updated successfully, but these errors were encountered: