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

Re: Use cases and requirements for Media Fragments: Chapter 8

From: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>
Date: Tue, 07 Apr 2009 23:40:56 +0200
Message-ID: <49DBC868.4070805@cwi.nl>
To: Conrad Parker <conrad@metadecks.org>
CC: Yves Lafon <ylafon@w3.org>, Media Fragment <public-media-fragment@w3.org>
Dear Conrad,

>> On the other hand, it seems to me that your proposal aims at solving the
>> problem of answering a complex request with multiple by ranges, while I do
>> not understand what the UA needs to do with the set of bytes it will receive
>> to have a playable resource.
>> Therefore, could you explain me what the 'Range-Referral' new header is
>> meant to do?
> 
> The user agent should concatenate the byte ranges to which it is
> referred. The semantics are that the resulting stream is equivalent to
> the stream that would otherwise be constructed for the segment
> (bytewise-identical, at least for the implementation I have in mind).

hum, so you assume that my fragment request will result into a number of 
multiple discontinuous sets of bytes in the original file? Why then 
would you like the client doing the concatenation and additional 
operation to get a playable resource? Why the server could not do that? 
It seems to me that you put the burden on the client.

> Perhaps "byte-range referral" is an accurate description of what's going on?

I will make an informal poll on the call :-)
Cheers.

   RaphaŽl

-- 
RaphaŽl Troncy
CWI (Centre for Mathematics and Computer Science),
Science Park 123, 1098 XG Amsterdam, The Netherlands
e-mail: raphael.troncy@cwi.nl & raphael.troncy@gmail.com
Tel: +31 (0)20 - 592 4093
Fax: +31 (0)20 - 592 4312
Web: http://www.cwi.nl/~troncy/
Received on Tuesday, 7 April 2009 21:41:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:32 GMT