Re: Public feedback on HTML5 video

>> Summarized Rationale:
>>
>> Avoid downloading video on pay per megabyte connections, and avoid
>> extra bandwidth from the publisher on video that won't be played.
>
> It seems reasonable to ignore the attribute *especially* on pay-per- 
> byte connections. If I'm on a pay-per-byte connection, I never want  
> to autobuffer video, even if the attribute is present.

Gruber's point was that *lack* of autobuffer attribute should not be  
ignored. Webkit's eager autobuffering is a real problem.

> On the flip side, when using a file: URL, it seems reasonable to  
> ignore the attribute and always autobuffer, since that leads to  
> better user experience and doesn't use any bandwidth.

I don't think that's a good use-case. Local file system should be as  
fast as cache and easily handle immediate playback. However if file://  
points to a network drive (sshfs, shared file server), autobuffering  
will waste bandwidth. If it's on a DVD disc, autobuffer may slow down  
loading of other resources (trashing due to long seek time).

I think the spec should say that browsers may ignore presence of  
autobuffer attribute, but must not autobuffer (from remote servers?)  
if attribute is not present.

-- 
regards, Kornel Lesinski

Received on Tuesday, 22 December 2009 16:32:55 UTC