- From: Philip Jägenstedt <notifications@github.com>
- Date: Thu, 06 Jul 2017 01:46:59 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 6 July 2017 08:47:30 UTC
> `new Audio("/path/to/media#t=30,60")` makes range request, yes? It does, but the requests should look roughly the same as when you do this: ```JavaScript var audio = new Audio("/path/to/media")` audio.currentTime = 30; audio.play(); audio.ontimeupdate = function() { if (audio.currentTime >= 60) audio.pause(); } ``` That's actually fairly close to how this is implemented. The media fragment is handled in the media element code, not at any lower level. If you want the server to do some of the work in slicing out 30-60 seconds, thenhttps://www.w3.org/TR/media-frags/#URIquery-media-fragments might be what you're looking for, but that then requires a clever server to interpret "/path/to/media?t=30,60". -- 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-313335148
Received on Thursday, 6 July 2017 08:47:30 UTC