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
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
Any protocol or subprotocol implementation should probably include a test case which ensures that multiple protocol sessions happening in parallel do not interfere with each other.
This may not be an issue if we stick to the practice of using Storage to manage all internal state variables, but it could be a good safeguard to have nonetheless
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Any protocol or subprotocol implementation should probably include a test case which ensures that multiple protocol sessions happening in parallel do not interfere with each other.
This may not be an issue if we stick to the practice of using Storage to manage all internal state variables, but it could be a good safeguard to have nonetheless
The text was updated successfully, but these errors were encountered: