-
Notifications
You must be signed in to change notification settings - Fork 30k
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
doc: guide on backpressure #10766
Comments
Hey @mcollina ! I am working on a light overview of streams as an exploratory project -- touched on backpressure a bit. But I would love to help with this issue to gain a deeper understanding! |
@jessicaquynh awesome! I would say, send a PR and we can start reviewing |
Awesome! Do you recommend following the structure of the existing guides ( ie. pick a project goal and then lead the reader there? ) |
@jessicaquynh I think so, but I will leave that to @nodejs/documentation. |
I'd say, give it a shot in any form. Good content is the best base, for getting this in. |
Note that there is a proposal about moving guides to node/nodejs.org: #10792 |
Would the best bet be to open up the PR on node/nodejs.org? I see that the transfer has yet to land officially, but would love some second opinions on my current draft! |
@jessicaquynh Yes, please do! |
I've opened up a PR on nodejs/nodejs.org, and would love anyone's input, if they care to share it! There's a more detailed description on what it is missing at the moment in the PR description and would love to collaborate for whoever is up for it! Thanks! :) |
@jessicaquynh good job!!! |
Since the guides have been moved to the nodejs.org repo and there's an open PR on this, I'm going to close this so that no one else tries to take it. If anyone feels that it really ought to stay open until that PR lands, feel free to comment or re-open. (I would suggest that we remove the |
There is no guide on streams backpressure, however this is one of the most advanced topics of Node.
I am very happy on reviewing the content.
This emerged from the discussion on #10631
cc @sam-github @nodejs/streams @nodejs/documentation
The text was updated successfully, but these errors were encountered: