> Yeah, my point was that in the perfect world, you'd support both at > runtime (at least on the server-side) and either ALPN or NPN could be > used. I want to have a library that supports both, not either-or.
Yes, supporting both at runtime would be best. But having a compile-time option now, and defaulting to NPN should keep this from being a blocking issue with the patch, correct? Thanks, Jeff Mendoza ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
