Hacker News new | ask | show | jobs
by alectic 1407 days ago
Streamed-response use cases get weird/complicated if you have to return the response.
2 comments

Not necessarily? The type used for Response can include a "body" type that supports streaming. E.g., body: AsyncRead in Rust. In Go I think it would resemble a channel that emitted the contents of the body.

(As a library, though, you'd also want to make the simple non-streaming case of "just return this blob of bytes" simple for the consumer, too.)

Sure but is that the usual / default? Why not have a second adapter?