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

Re: a quick scan of RTSP for media fragments

From: RaphaŽl Troncy <raphael.troncy@eurecom.fr>
Date: Wed, 30 Jun 2010 11:46:20 +0200
Message-ID: <4C2B126C.2010203@eurecom.fr>
To: Jack Jansen <Jack.Jansen@cwi.nl>
CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Davy Van Deursen <davy.vandeursen@ugent.be>, public-media-fragment@w3.org
Hi all,

> I agree with all of your examples (thanks!), except one:
>
>> Re (1): In RTSP, temporal fragment URIs are provided through the
>> PLAY method:
>>
>> a url such as
>>
>> rtsp://example.com/media#t=10,20
>>
>> will be executed as a series of the following methods (all
>> shortened for readability), data selection provided in the PLAY
>> method:
>>
>> * C->S: DESCRIBE rtsp://example.com/media * S->C: RTSP/1.0 200 OK
>> (with an SDP description, see wiki) * C->S: SETUP
>> rtsp://example.com/media/video * S->C: RTSP/1.0 200 OK * C->S:
>> SETUP rtsp://example.com/media/audio * S->C: RTSP/1.0 200 OK *
>> C->S: PLAY rtsp://example.com/media Range: npt=10-20 * S->C:
>> RTSP/1.0 200 OK Range: npt=9.5-20.1
>
>
> Why do you use two SETUP commands for separate tracks here? Shouldn't
> you simply do a single "SETUP rtsp://example.com/media"?

Good question! Silvia?

   RaphaŽl

-- 
RaphaŽl Troncy
EURECOM, Multimedia Communications Department
2229, route des CrÍtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.eurecom.fr/~troncy/
Received on Wednesday, 30 June 2010 09:48:32 GMT

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