[MPlayer-dev-eng] [PATCH] libmpdemux/realrtsp handling url parameters (start|end)=hh:mm:ss.msec

[Roberto Togni]

On 2003.11.17 14:54, rgselk wrote:
> --- Attila Kinali <kinali at gmx.net> wrote:
> > On Mon, 17 Nov 2003 02:32:29 -0800 (PST)
> > rgselk <rgselknospam at yahoo.com> wrote:
[...]
> The first is a patch to use the parameters 'start' and 'end' in the
> url
> to set the rtsp 'Range' parameter.
> Last Friday I discovered that realplay still uses the complete url in
> the request, so I changed the patch to do the same.
How does this patch relate to the patch proposed in thread  
http://www.MPlayerHQ.hu/pipermail/mplayer-dev-eng/2003-August/019928.html

At that time it was not applied. Tha author claimed that the server did  
not like the part following the ? in the url; in his case he had ""  
around the time values (urls coming from .ram files).
Maybe we should remove them if coming from ram files (or if they have  
"") and keep them in other cases?
In another mail from that thread Ross from live.com said that clients  
should not parse query strings in urls, because it's the server that  
have to do it; but maybe with Real proprietary protocol that's not  
true.

Do you have any idea on the matter?

BTW, these patches and your other ones are identical (the only  
difference is that  two debuf printf are commented out):it this the  
right version or do you still have to send the modified patch that does  
not remove the urls?
> 
> The second patch is to find the string .rm or .ra followed by a '?'  
> or
> '&' or at the end of the string. This allows for detecting a real  
> rtsp
> url even when there is another '.' in the string. (for example in the
> millisecond part of the start tag: hh:mm:ss.msec).
This part should be applied anyway, else those urls won't be recognized  
as Real streams.

[...]
I see you're now working on Real rtsp keyframes and seeking: is it  
still ok to apply this patch or will it be obsoleted by your future  
patches?

> Regards,
>   rgselk.
Ciao,
 Roberto