-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accept AsyncIterator as an HTTP request body #221
Comments
I support this 100%!! But why just uint8array? AsyncIterator<string> could be allowed as well? |
I think it could be See the current HttpRequestBody for reference: Line 12 in fc9d854
|
Yes, sounds excellent. |
@jeremymeng Is this applicable for the new Azure Core v2? If so, please create a new issue in the azure-sdk-for-js repo and close this issue |
See the article on async iterators: https://jakearchibald.com/2017/async-iterators-and-generators/
This is probably only for nodejs, at least to start with, because browsers don't support streaming request bodies (not even fetch at this point, even though it's in the spec). This is a more modern alternative to the nodejs stream interface.
@bterlson may wish to comment on this
The text was updated successfully, but these errors were encountered: