Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ws: Concurrent Error Handling Model #4

Open
niaow opened this issue Jul 16, 2019 · 0 comments
Open

ws: Concurrent Error Handling Model #4

niaow opened this issue Jul 16, 2019 · 0 comments
Labels
bug Something isn't working enhancement New feature or request help wanted Extra attention is needed question Further information is requested

Comments

@niaow
Copy link
Owner

niaow commented Jul 16, 2019

So I have realized that some of my concurrent error handling model was flawed. My main goal is to find the root cause error and return it everywhere relevant. However, there are many edge cases which can complicate this, like both ends attempting to close the connection at once - where it is entirely possible that a read error will cause the write end to act as if it completed a successful closure. I may have to rethink some of this.

@niaow niaow added bug Something isn't working enhancement New feature or request help wanted Extra attention is needed question Further information is requested labels Jul 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant