Hi Ross,
Perhaps Don Quixote wrote RFC 2326 chapter 12.19...
More seriously we need to seek in absolute mode because we would like to query
video according to the time we recorded it (and not a relative time relative to
begin of RTSP session).
I try to find ways to reduce live555 patching (I would like to use live555
wihtou any patch).
But without entry point in RTSPClient, I guess we have no others way that
patching it ?
Thanks & Regards,
Michel.
[@@THALES GROUP RESTRICTED@@]
De : live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] De la part de Ross Finlayson
Envoyé : mercredi 23 mai 2012 12:35
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] How to specify Range in RTSPClient that are not using
npt
We try to find a way to send a range in absolute, it seems that a way could be
to specify in the RTSP PLAY command :
- Range: clock=19961108T142300Z-19961108T143520Z
Why? Once again, I don't see the point. With a "Range:" header like this (in
fact, any "Range:" header other than "0-" or "now-"), you're telling the server
that you want to seek. But if the server's not going to be seeking within the
stream, then there's no point in sending a header like this. (And in fact, our
server code doesn't even handle this kind of "Range:" header (and there are no
plans to extend it to do so, because noone ever uses it.)
I don't understand why you keep "tilting at this windmill".
Is it possible to define this method in the RTSPClient class as virtual in
order to extend it ?
I have no plans to do this. Again, I just don't see the point...
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
