Re: [w3ctag/design-reviews] Fetch streaming upload (Issue #754)

> "Currently when users need to do xxx the situation is yyy. This creates problems because zzz. This technology solves these problems by qqq."

I think they are already explained in the doc.

The end-user benefit is described as:

> These performance shortcomings and cost of additional logic will impact end-users. In other words, this feature will help end-users enjoy web applications with better performance, more reliability and less cost.

Sample use-cases are listed as:

> - Web developers can upload unbounded data to the server.
> - Web developers can implement streaming processing easily.

The kwown workarounds and their shortcomings are described at the `Without the feature` paragraph.

I like the current structure because xxx, yyy and zzz are long.  If we had them in a single paragraph, it'd be very hard to understand the paragraph.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/754#issuecomment-1276314467
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/754/1276314467@github.com>