On Thu, May 5, 2016 at 12:46 AM, Thierry Foucu <tfo...@gmail.com> wrote: > On Wed, May 4, 2016 at 1:58 PM, Derek Buitenhuis <derek.buitenh...@gmail.com >> wrote: > >> On 5/4/2016 9:52 PM, wm4 wrote: >> > This was never allowed and was never public API. Use custom I/O instead >> > (creating an avio context with your own read/write callbacks). >> >> > Can i ask why it cannot be part of the public API? > It was really practical just to register new prefix, specially, when you > have to create X number of them. > I think this should be a feature. We allow to register filter, codec, > muxer/demuxer, why not URL >
While technically it is possible to register those, in practice you would need to use a bunch of internal APIs to properly implement any of those externally, so its not really possible. ffurl has been private forever now, and making it public would require a proper documented, supported and stable API and ABI, which is not something that should be taken lightly. The URL API has not been public for years and years, so nothing really changed for a long time, except the internal implementation of private functionality. There is an alternative to use avio, which is what will remain the standard way to hook in custom IO functionality. - Hendrik _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
