webhoster VS readable-stream

It's way simpler than it sounds. This is a < 100 line implementation, server-side.

I had written my own in-house framework to fully support HTTP2 and performance is slightly better than Koa.

I have an extremely similar setup, but not 100% to spec because I wrote a HTTP server in node and it has some expectations of being used for HTTP requests. But most of Response is built into the API, with expectation that you would interface with an HTTP request in the same fashion as a service worker. The public version is out of date, but the internal version I have used has the stream consumers. I use it for HTTP2 Push setup.

If it's a readable stream, you can just directly consume it with an async iterator: https://nodejs.org/api/stream.html#streams-compatibility-wit...

Node.js Stream

Note that the older Node.js streams API hasn't been deprecated or removed. It will co-exist with the new API, and it even provides a way to convert from a web stream and vice versa using the .fromWeb() and .toWeb() methods (both added in Node 17, although both methods still retain their experimental status).

Nodejs has piepes with its stream https://nodejs.org/api/stream.html

You then want what's invoked by that event to be consumed as a Response. NodeJS has something to replicate this with stream consumers where you can do all the response.text() you normally do.

[3] - https://github.com/nodejs/readable-stream/

First, we create a NodeJS ReadStream using fs.createWriteStream to open the test.log file in "append" mode. Then we start recursively looping using setTimeout. This simulates an application that logs text in the file at a variable rate. At each iteration:

This needs a comparison with streams, which is the standard way to achieve this in Node.js land.

https://nodejs.org/api/stream.html