ISSUE-11: How the UA knows the full media duration when only a fragment is served?

Duration-header

How the UA knows the full media duration when only a fragment is served?

State:
CLOSED
Product:
Raised by:
Silvia Pfeiffer
Opened on:
2009-08-18
Description:
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?
Related Actions Items:
No related actions
Related emails:
  1. RE: ISSUE-11 (Duration-header): How the UA knows the full media duration when only a fragment is served? (from davy.vandeursen@ugent.be on 2009-09-03)
  2. Re: ISSUE-11 (Duration-header): How the UA knows the full media duration when only a fragment is served? (from Raphael.Troncy@cwi.nl on 2009-09-02)
  3. RE: ISSUE-11 (Duration-header): How the UA knows the full media duration when only a fragment is served? (from ylafon@w3.org on 2009-09-02)
  4. RE: ISSUE-11 (Duration-header): How the UA knows the full media duration when only a fragment is served? (from Franck.Denoual@crf.canon.fr on 2009-08-26)
  5. Re: ISSUE-11 (Duration-header): How the UA knows the full media duration when only a fragment is served? (from Raphael.Troncy@cwi.nl on 2009-08-19)
  6. minutes of 2009-08-19 teleconference (from Raphael.Troncy@cwi.nl on 2009-08-19)
  7. RE: Media Fragments Working Group: Agenda 19 August, Telecon 1200 UTC (from davy.vandeursen@ugent.be on 2009-08-19)
  8. Re: Media Fragments Working Group: Agenda 19 August, Telecon 1200 UTC (from michael.hausenblas@deri.org on 2009-08-18)
  9. Media Fragments Working Group: Agenda 19 August, Telecon 1200 UTC (from Raphael.Troncy@cwi.nl on 2009-08-18)
  10. Re: Fwd: [whatwg] Remove addCueRange/removeCueRanges (from Raphael.Troncy@cwi.nl on 2009-08-18)
  11. ISSUE-11 (Duration-header): How the UA knows the full media duration when only a fragment is served? (from sysbot+tracker@w3.org on 2009-08-18)

Related notes:

This issue has been discussed 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.

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

Raphaël Troncy, 19 Aug 2009, 17:24:05

Display change log ATOM feed


Raphaël Troncy <Raphael.Troncy@eurecom.fr>, Erik Mannens <erik.mannens@ugent.be>, Chairs, Yves Lafon <ylafon@w3.org>, Thierry Michel <tmichel@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 11.html,v 1.1 2014-07-24 14:16:40 vivien Exp $