Can't handle backpressure correctly with response.write about hyper-express HOT 3 CLOSED

uWS.write() usage is already implemented in 5.1.2 for streaming and the total_size parameter is now optional. No need to use a Writable as the stream method directly consumes data from the Readable stream and pauses/resumes as uWebsockets allows for more chunks to be served with backpressure handling. You can look at source in src/components/Response.js for how stream method works under the hood. In regards to the actual method returning the actual method returning the Boolean, will get that added in next update.

from hyper-express.

I can't use the response in a pipeline without this...

Also, the express response implements writable, so you don't have parity with express until this is implemented.

I guess I'll use a different framework...

from hyper-express.

See 5.3.0 for the new changes in which Response.write() now returns a Boolean similar to Response.send() and other write based methods. Also, Response.drain() has been implemented to work in conjunction with Response.write() when implementing your own backpressure strategy. Also, a Response.writable property has been imlemented which returns a Writable stream associated with the response so you can pipe your readable into it.

The goal with hyper-express is not to have 100% parity with express as uWebsockets.js is fundamentally different from express in how it works and handles the request lifetime flow. Most of the uWebsockets.js methods do not handle backpressure themselves and thus for consistency with the underlying driver of this package, this behavior is extended to the methods of HyperExpress as well.

from hyper-express.