Hi, as i'm working on VTest HTTP/3, this discussion is of particular intrest to me. Still WIP, i have not shared any code, thus i assume most of you are not aware of my efforts, so thanks for considering my opinion.
I used ngtcp2/nghttp3 and implemented the needed VUDP* equalents for what is VTCP* in Varnish as well as its VTest copy (see lib/vtcp.h). To me it would make much sense to have it in a shared library, basically the "varnish-lib" idea. Of course it would mean, that it would be OK, to have (at least optional) dependencies on ngtcp2, nghttp3 and a SSL Library*. IIRC HAproxy already have an other HTTP/3 implementation, so i would assume they would not be intrested, in using "varnish-lib" outside of VTest, but there might still be room for collaboration in the future. For Varnish, i think it would make sense to use the poposed lib for HTTP/3, i would keep the server init (TLS Key reading etc.) out of the shared lib, so Varnish can still use other means (keyless). * ATM i use WolfSSL as my OS comes with a LibreSSL without Quic support, however, new enough OpenSSL, its derivates and GNUtls can be used with ngtcp2 Julian -- ** * * UPLEX - Nils Goroll Systemoptimierung Scheffelstraße 32 22301 Hamburg tel +49 40 60945064 http://uplex.de/ _______________________________________________ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
