Guillaume (Jean-Louis) Olivrin
Davy Van Deursen
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?
Add notes (no markup allowed, URIs get automatically hyperlinked):
This issue has been discussed during the 19/08/2009 telecon . Yves confirmed that a normal HTTP response (206) to a HTTP range request will do the job. The wiki page , 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.