Re: [w3c/FileAPI] Streams is hot, FileReader.readAs____ is not (#40)

That sounds about right. I think for `FormData` we concluded that exposing the size would be too hard (due to various encodings being in play). (We could also consider `URLSearchParams` I suppose, although that stringifies so maybe not.)

I guess the other question is whether there is some ToStream operation that takes an arbitrary object and invokes `toStream()` on it. Whether there's a protocol in play or just some consistency we try to enforce. (And if there's a protocol in play we might not want to use a method invocation to let browsers more easily make certain optimizations.)

As for `Content-Length`, we're unsure how that can work in general for stream uploads (and not needed in H2 aiui) since we need to take into account that the developer might be malicious. It might be best to simply not support `Content-Length` use cases since it's going away anyway.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/40#issuecomment-249805662