On 10/13/11 3:51 PM, Martin Storsjö wrote:
On Thu, 13 Oct 2011, Luca Barbato wrote:
On 10/13/11 2:02 PM, Martin Storsjö wrote:
Additionally, that still has the issue of parsing options from URLs and
redirects - if I give the input url rtsp+tcp://foo/bar, which redirects
me to rtsp://other/server, I'll reparse that url, forgetting about the
options passed in the previous one. Sure that can be fixed by even more
kludges, but that's all what I'm trying to get rid of here.
You made a good point. I'd keep this syntax and use it to fill the
options but might be just overkill.
Keep which one, the current, or the new with rtsp+tcp://?
The new one.
The current
one is just crap IMO, but rtsp+tcp:// would be more convenient, I do
agree about that. The downside would be that we'd have two different
nondeprecated ways of doing one thing, which is confusing and inconsistent.
only if you mix them up, but yes it might cause more harm than good.
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
