W3C home > Mailing lists > Public > public-media-fragment@w3.org > May 2010

Re: Notify user agent available fragment

From: RaphaŽl Troncy <raphael.troncy@eurecom.fr>
Date: Wed, 05 May 2010 17:00:20 +0200
Message-ID: <4BE18804.6000308@eurecom.fr>
To: Jeroen Wijering <jeroen@longtailvideo.com>
CC: public-media-fragment@w3.org
Dear Jeroen,

> I personally think it would be good to do return a 4xx error (out of
> range?) when the requested data entirely lies outside the range of the
> mediafile:
> * An audiotrack is requested for a mediafile that only contains video.
> * A fragment from 50 to 60 seconds is requested for a mediafile that is
> only 30 seconds in length.
> * A region from 400x300 to 600x300 is requested for an image that is
> only 200x300 in size.
> In each of these cases I'd presume the full mediafile has little value
> to the user agent (why video if I requested audio? why 0-30s if I
> requested 50-60s? it's the wrong data and I either cannot or don't want
> to present it to the user.). Returning the entire resource by default
> would seem to generate a lot of traffic for data that will likely not be
> used. In case of the error, the user agent can always fallback to a
> request for the full resource in such rare cases it does want it.

Thanks for your input. Some of these error cases you mentioned (and 
others) are currently discussed at 

For example, your second error case ("A fragment from 50 to 60 seconds 
is requested for a mediafile that is only 30 seconds in length"), 
corresponds to the Test Case nį9 and we indeed foresee a 416 response 
(The request lies beyond the end of the resource).


RaphaŽl Troncy
EURECOM, Multimedia Communications Department
2229, route des CrÍtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~troncy/
Received on Wednesday, 5 May 2010 19:24:42 UTC

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