On Tue, Aug 21, 2012 at 11:12 PM, aviad rozenhek <[email protected]> wrote:
> On Tue, Aug 21, 2012 at 6:43 PM, Luca Barbato <[email protected]> wrote: > >> On 8/21/12 5:34 PM, aviad rozenhek wrote: >> >>> Hi, >>> >>> in recent versions of libav, URLProtocol has moved to a new header url.h, >>> which is not installed by make install. >>> URLProtocol allows an application to extend libav by adding new types of >>> protocols or modifying the behavior of existing protocols without >>> changing >>> libav code. >>> this is extremly useful behavior. >>> >> >> Agreed, avio covers most of the needs but a few might require going lower >> level. >> >> >> would it be possible to make URLProtocol available to application >>> developers again? >>> >> >> During the avserv project that had been a discussion item, mostly it just >> requires to see what can't be done using the normal avio and how to lay out >> the avproto(?) api so it works for everybody. >> >> Proposals are welcome. >> >> lu >> > > > I think URLProtocol was declared 'deprecated' about a year ago [during the > 'big bump' period] > it did receive some changes since then including improvements to options > and to interrupts, which is nice. > yet from what I see the protocols are pretty stable and not much work > going on there. > perhaps it makes sense to just rename URLProtocol to AVProtocol? > > > sadly, because of not being regarded as public, the URLProtocol functions like ffurl_open, ffurl_close and such are not exported by .DLLs generated in libav builds. this makes porting my application to new builds of libav impossible until URLProcotol is considered public again. is there any reason to refrain from making them public? -- Aviad Rozenhek
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
