On Sat, 23 May 2015, wm4 wrote:

On Fri, 22 May 2015 22:25:53 +0300 (EEST)
Martin Storsjö <[email protected]> wrote:

On Fri, 22 May 2015, wm4 wrote:

A separate alternative would be to name the protocol structs differently, i.e. naming them ff_tls_gnutls_protocol, ff_tls_openssl_protocol, etc. Then you'd have separate register-entries for them in allformats.c, and you'd handle the mutual exclusion in configure like this: tls_openssl_protocol_deps="!tls_gnutls_protocol" (see rtmp_protocol vs librtmp_protocol).

I'd prefer this.

Ideally though, there'd be some way to "redirect" a protocol to a
certain implementation. It could even switch the implementations at
runtime, which might be useful for debugging.

Indeed. Even if we don't have that mechanism in place, we'd have the same situation as for rtmp, potentially multiple implementations, only lacking a sensible way of selecting which one to use (currently probably picking the first one registered, i.e. alphabetically).

// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to