On Wed, 29 Jan 2014, Fabian Frank wrote:
Do we already want to introduce ifdefs for backwards compatibility at this point? HTTP2 and nghttp2 are moving so fast and nothing is finalized yet, so it might make the code easier to maintain in the long run if we just mandate an exact (or the latest) nghttp2 version until things are more stabilized. What do you think?
Yeah lets go with "latest nghttp2" for now at least until nghttp2 stablizes somewhat and before we ship a release where people can actually use http2.
We could possibly add #ifdefs to #error out on early versions we know will fail. Later on, we can fix the configure check to also reject old versions.
-- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
