[rtmpdump] Need help with rtmpdump url parser

Petr Pisar petr.pisar at atlas.cz
Fri Dec 16 09:25:01 CET 2011

On Thu, Dec 15, 2011 at 06:53:04PM -0800, Howard Chu wrote:
> Manuel Reimer wrote:
> >Howard Chu wrote:
> >>The parser logic is not flawed. The RTMP specification is flawed.
> >
> >So the only way to fix this in this case, is to patch the parser to handle
> >"ardfs" the same way as "ondemand"?
> >
> >In my case it is no solution to use the parameters to pass the options
> >separately as I want to pass the URL to mplayer.
> mplayer "rtmp://foo:1935 app=blah/blah playpath=x/y/zzz"
Which is still not a valid URI (because of the space characters). AFAIK there
is no rtmp URI schema standard. What about abadone this spacy hack and
introduce new format that will be formally URI (or URL more precisly). E.g.
"rtmp://foo:1935/?app=blah/blah&playpath=x/y/zzz". Of course some characters
in parameter (e.g. ampersands and equals in parameter names and values) must
be properly escaped.

-- Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 230 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/rtmpdump/attachments/20111216/48205d63/attachment.asc>

More information about the rtmpdump mailing list