W3C home > Mailing lists > Public > public-media-fragment@w3.org > August 2009

Re: ISSUE-11 (Duration-header): How the UA knows the full media duration when only a fragment is served?

From: Raphaël Troncy <Raphael.Troncy@cwi.nl>
Date: Wed, 19 Aug 2009 19:30:23 +0200
Message-ID: <4A8C36AF.5030300@cwi.nl>
To: Media Fragments Working Group WG <public-media-fragment@w3.org>
Dear all,

We have discussed the ISSUE-11 during the 19/08/2009 telecon [1]. Yves 
confirmed that a normal HTTP response (206) to a HTTP range request will 
do the job. The wiki page [2], which was incomplete, has been updated. 
More precisely, the content-range header in the response will have as 
value something in the line of:

   Content-Range: seconds 11.85-21.16/3600

indicating thus the total duration of the parent resource. The UA will 
be able to display the complete timeline of the resource.
I have closed this ISSUE in the tracker.


[1] http://www.w3.org/2009/08/19-mediafrag-minutes.html
[2] http://www.w3.org/2008/WebVideo/Fragments/wiki/HTTP_implementation

Media Fragments Working Group Issue Tracker a écrit :
> ISSUE-11 (Duration-header): How the UA knows the full media duration
> when only a fragment is served?
> http://www.w3.org/2008/WebVideo/Fragments/tracker/issues/11
> Raised by: Silvia Pfeiffer On product:
> An issue with any of our existing specs with fragments (#) that just
> occurred to me is: if the retrieval action only retrieves the
> specified segment, the browser has no way to figure out the length
> (start/duration) of the original resource. Maybe we need to introduce
> additional headers that would provide for that?

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.cwi.nl/~troncy/
Received on Wednesday, 19 August 2009 17:31:03 UTC

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