Re: [whatwg/fetch] Allow range header to be set by APIs (#560)

> @guest271314 media fragments are an instruction to the media element, which then makes the appropriate fetches with the correct Range headers. It may be many fetches too, as it'll need to download metadata so it can translate the temporal ranges into byte ranges.
> 
> fetch("/media#t=30,60") only fetches, it doesn't perform media decoding, so it'd be a bit weird if this call made multiple requests, decoded parts of the media, and chopped the response up.

Well, from perspective here, that would not be a "weird" result. That precise application is what was attempting to describe at https://github.com/whatwg/fetch/issues/555. 

That is what initially read when browsing the concept of `type` and `destination` at the specification, though apparently that is not the case.

That is, how to set the context of a `fetch()`, `Request()` or `Response()` call at if the target was a `HTMLMediaElement`. In effect using `fetch()` as a proxy, where the network request would appear to be generated by, for example, `new Audio()`. Not sure if that degree of control is beyond the scope of present inquiry. 

We have `.blob()`, why cannot we have `.mediaFragment()`, i.e.g., https://github.com/whatwg/fetch/issues/554#issuecomment-312331259?

-- 
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/fetch/pull/560#issuecomment-312921749