W3C home > Mailing lists > Public > public-media-fragment@w3.org > March 2010

Re: ACTION-155: Figures illustrating URI fragment Resolution in HTTP

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Tue, 23 Mar 2010 10:16:43 +1100
Message-ID: <2c0e02831003221616r3b494c50g9bc0605fcfbfbdd0@mail.gmail.com>
To: Davy Van Deursen <davy.vandeursen@ugent.be>
Cc: public-media-fragment@w3.org
Hi Davy,

5.2.1-5.2.3 look fine to me in both cases.

5.2.4 is interesting. The replies on 5.2.4 will actually always need
to have a multipart message body reply (multipart/byteranges), because
there will be setup bytes and data bytes, so it will basically look
like 5.2.2 in the multiple byteranges section, but also include the
header data.
Also, it still needs an additional request header - maybe the Range
header could be extended to be:
Range: t:npt=11-19;include-setup
?

Cheers,
Silvia.


On Mon, Mar 22, 2010 at 11:21 PM, Davy Van Deursen
<davy.vandeursen@ugent.be> wrote:
> Dear all,
>
>
>
> at [1], you can find a number of figures showing which bytes from the
> headers and body of the media file are sent, depending on the four cases we
> have defined (cfr. 5.2.1, 5.2.2, 5.2.3, and 5.2.4). Any comments are
> welcome. After processing these comments, I will save them as images and
> integrate them into the spec.
>
>
>
> Best regards,
>
>
>
> Davy
>
>
>
> [1]
> http://www.w3.org/2008/WebVideo/Fragments/wiki/images/3/38/Mediafragmentheaders.pdf
>
>
>
> --
>
> Davy Van Deursen
>
>
>
> Ghent University - IBBT
>
> Faculty of Engineering
>
> Department of Electronics and Information Systems
>
> Multimedia Lab
>
>
>
> Gaston Crommenlaan 8 bus 201
>
> B-9050 Ledeberg-Ghent
>
> Belgium
>
>
>
> t: +32 9 33 14893
>
> f: +32 9 33 14896
>
> t secr: +32 9 33 14911
>
> e: davy.vandeursen@ugent.be
>
> URL: http://multimedialab.elis.ugent.be/dvdeurse
>
>
Received on Monday, 22 March 2010 23:17:40 GMT

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