- From: Ben Wiley <notifications@github.com>
- Date: Thu, 05 Nov 2020 14:43:03 -0800
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 5 November 2020 22:43:15 UTC
Personally I could benefit a lot from the ability to turn an arbitrary readable stream into a URL. I have a download button for large files, which must wait for a multipart data fetch to complete (this is the only fetch method currently available to me), parse a `File` from the result, then use the invisible anchor tag hack to initiate a download. This means the user isn't able to do anything nice like watch the progress as the file downloads, or open the file in a new tab and wait for it to load. Just a long pause and then... all downloaded! What would be much better is if I could take a `ReadableStream` of the main file content which itself would read the `body` stream of the Fetch API (I already have this for streaming text and video content onto the page). Then I could create a URL out of that stream and its content type, render an `<a>` tag, and the browser could either load it in a separate tab or initiate a client download. I don't know how niche my use case is, but to be able to solve it would be extremely cool. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/480#issuecomment-722687719
Received on Thursday, 5 November 2020 22:43:15 UTC