- From: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Date: Wed, 22 Jun 2011 10:04:58 +0200
- To: Davy Van Deursen <davy.vandeursen@ugent.be>
- CC: Media Fragment <public-media-fragment@w3.org>
Hi Davy, > Since the requested time range is invalid, the server answers with a 416 > (Requested Range Not Satisfiable), and the UA still doesn't have a clue > about the duration of the media. > > So the question is, what is the behaviour of a UA getting a 416 from a > Media Fragments-enabled server (especially in the case when the decoding > pipeline is not setup)? > > I think this situation must be clarified in the spec. I'm unsure how we have finally closed this discussion: * In the case of not satisfiable *time* range, as Silvia pointed out, the server will provide the indication of the entire duration of the media so that solves the problem. * In the case of a non-existent track, I'm not sure we should talk about a "not satisfiable requested range" (416). I guess this will be clarified when we go through these test cases. Raphaël -- 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, 22 June 2011 08:05:25 UTC