- From: Jack Jansen <Jack.Jansen@cwi.nl>
- Date: Tue, 29 Jun 2010 22:12:19 +0200
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Davy Van Deursen <davy.vandeursen@ugent.be>, public-media-fragment@w3.org
On 28 jun 2010, at 10:50, Silvia Pfeiffer wrote: [...] > So, I want to take a step back and summarise some of the things that > were discussed here and in the wiki and put it into a structure that > we can use for the spec. 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"? -- Jack Jansen, <Jack.Jansen@cwi.nl>, http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman
Received on Tuesday, 29 June 2010 20:12:57 UTC