James Almer (12020-07-14): > Perhaps this should instead be implemented as an AV_OPT_TYPE_DICT option > that can accept anything you would otherwise pass as part of the url, so > user, pass, port, etc.
It makes things more complicated for us (accessing a dictionary instead of options directly), for API users (setting the dictionary plus the option itself) and for command-line users (extra level of escaping). Unless we expect the list of things obtained from the URL to grow in the future, which is unlikely to say the least, I see no benefit compared to just adding all this at once. Am I missing something? What benefit would you expect? On the other hand, since a lot of protocols do some kind of av_url_split(), it makes sense to factor it. Why not add all these fields to URLContext and have ffurl_connect() split the URL, using options if they are available? Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
