Skip to content

Readable stream with ack #324

@domenic

Description

@domenic

An idea that keeps coming up (most recently #323, feel free to edit this post to point to other instances) is "readable stream with ack," i.e., one that not only lets you read(), but also lets you acknowledge when you're done with a chunk.

The most compelling case for this has to do with buffer re-use (e.g. #323). It also gives some symmetry with writable streams' two-signals approach (but see #316).

However, I find it basically impossible to envision author code using this correctly and consistently. @tyoshino, could you help illustrate some author code that operates like this?

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions