W3C home > Mailing lists > Public > public-media-fragment@w3.org > December 2008

Re: Backwards compatibility and the use cases and requirements draft

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 17 Dec 2008 19:13:12 +1100
Message-ID: <2c0e02830812170013p5b4612c8k3d56e8d2cc8dcf19@mail.gmail.com>
To: "Geoffrey Sneddon" <foolistbar@googlemail.com>
Cc: "Media Fragment" <public-media-fragment@w3.org>

Ah yes, that's just the wiki page, but we will indeed put a version of
this into the use cases and requirements section of the specification.

I've added a blurb at the end of the "side conditions" section on that
wiki page about fallback solutions. After having thought about it a
bit more, it is probably not a good idea to do the full media resource
download by default. For example, think about a media fragment URI to
an offset of 15 hours into a 20 hour long video for a 2 min long
fragment. Think about such a request on a mobile phone. With almost
certainty, you do not want your phone to just go off and download the
full resource instead of the 2 min excerpt.

So, I think the user agent should inform the user of the failed
fragment URI and give the user the option to get the full resource,
but not do it by default.

Also, if your user agent does not support media fragment URIs, then it
will by default send a request for the full resource to a media server
(since the #-part of the URI is only a client-side interpreted part of
the URI).


On Wed, Dec 17, 2008 at 9:04 AM, Geoffrey Sneddon
<foolistbar@googlemail.com> wrote:
> On 16 Dec 2008, at 20:34, Silvia Pfeiffer wrote:
>> Actually, there is no specification available yet, so I wonder what
>> draft you are referring to. :-)
> <http://www.w3.org/2008/WebVideo/Fragments/wiki/Use_Cases_%26_Requirements_Draft>
> as the subject may hint at. :)
> --
> Geoffrey Sneddon
> <http://gsnedders.com/>
Received on Wednesday, 17 December 2008 08:13:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:41 UTC