Streaming types / APIs in standard library

Use Case

• Downloading a file from a bucket and saving it directly to disk
• Downloading a file from an HTTP response, and performing processing on its output
• Reading a file from disk as a stream, and processing it piece by piece (e.g. to count how many lines it has)
• Streaming a response back from an API endpoint written by the user

Proposed Solution

Dedicated streaming APIs that don't require the entire contents of an API response or file or etc. to be loaded in memory at once.

(side note: maybe file streams and HTTP streams should be treated separately? I'm not sure)

Implementation Notes

References:

• https://streams.spec.whatwg.org/#readablestream
• https://developer.mozilla.org/en-US/docs/Web/API/Streams_API
• https://docs.python.org/3/library/io.html
• https://docs.python.org/3/library/asyncio-stream.html
• https://hexdocs.pm/file_streams/file_streams/file_stream.html

Component

SDK

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.
• If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out on the #dev channel in the Wing Discord.

No implementation files, tests, or entry points are identified in the issue. Start by reviewing the linked WHATWG, MDN, Python, and Elixir streaming references and clarify whether file and HTTP streams share an API. Done means the SDK streaming API scope and specification are finalized, with the unresolved design questions addressed.