W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2009

[whatwg] <video>/<audio> feedback

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 30 Apr 2009 16:37:58 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0904301636510.7824@hixie.dreamhostps.com>
On Thu, 30 Apr 2009, Silvia Pfeiffer wrote:
> 
> Because media fragment URIs will not deliver the full resource like a 
> HTML page does, but will instead only provide the segment that is 
> specified with the temporal region. http://example.com/video.ogg#t=5s 
> only retrieves the video from 5s to the end, not from start to end.
> 
> So you cannot scroll to the beginning of the video without another 
> retrieval action: i.e. assuming we displaying the full video timeline 
> for a <video src="http://example.com/video.ogg#t=5s"..> element, and 
> then the user clicks on the beginning of the video, a 
> http://example.com/video.ogg#t=0s request would be sent.
> 
> The difference is the need for the additional retrieval action, which, 
> if the full resource was immediately downloaded for 
> http://example.com/video.ogg#t=5s would not be necessary. But that's not 
> how media fragments work, so I tried pointing this out.

It's generally understood that videos wouldn't be downloaded all at once 
anyway; UAs are expected to download the bits they want to cache, jumping 
in and out of the resources as the user seeks, etc. So this doesn't seem 
like a major difference to me.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 30 April 2009 09:37:58 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:11 UTC