W3C home > Mailing lists > Public > public-media-fragment@w3.org > October 2008

Re: video use-case

From: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>
Date: Wed, 08 Oct 2008 09:54:47 +0200
Message-ID: <48EC6747.2040302@cwi.nl>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
CC: Dave Singer <singer@apple.com>, Media Fragment <public-media-fragment@w3.org>

Dear Silvia,

> I won't have the time to go into details, but I studied it 7 years ago
> as we were defining temporal URIs. Essentially: the play request has a
> range parameter as part of the protocol parameters of RTSP (see
> http://www.ietf.org/rfc/rfc2326.txt and search for range). It is the
> equivalent of what Dave and I have been discussing: the use of byte
> ranges to deliver the data. However, in HTTP we need to have a
> mechanism to communicate the temporal segment (or more generally: the
> media fragment) between a user, a user agent, and a server, such that
> the server can help convert the fragment to a byte range, which in
> turn the UA can then request from the server and can be proxied by
> intermediates.
> I'll make a picture of it, since it seems this is difficult to
> understand. We only have very few possibilities of how we can do this
> communication because of the way in which video resources, HTTP, and
> URIs work. I don't have much time today to get onto it but will what I
> can.

Thanks for the explanation, I have slightly updated 
http://www.w3.org/2008/WebVideo/Fragments/wiki/Issues#Protocols for the 
Best regards.


RaphaŽl Troncy
CWI (Centre for Mathematics and Computer Science),
Kruislaan 413, 1098 SJ 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 Wednesday, 8 October 2008 07:59:01 UTC

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