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

Consider backpressure #65

Open
mehaase opened this issue Oct 23, 2018 · 0 comments
Open

Consider backpressure #65

mehaase opened this issue Oct 23, 2018 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@mehaase
Copy link
Contributor

mehaase commented Oct 23, 2018

Preface: I don't know if this issue will be resolved by writing code, writing docs, or both. I'm starting this thread just to document some of the issues around backpressure and potential solutions.

The library has no special mechanics or documentation to deal with the important issue of backpressure. This is an area of concern for me because I once spent a long time debugging a backpressure problem in aaugstin's websockets, and at the time I didn't even know what the term meant!

At the library level, we can avoid backpressure issues by making sure not to have any unbounded buffers inside the library. At the user level, we probably need some documentation so that they are also aware of this issue and can avoid it.

@mehaase mehaase added the enhancement New feature or request label Nov 17, 2018
@mehaase mehaase added this to the 1.0 milestone Nov 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant