Lines Matching +full:high +full:- +full:performance
9 -------------------------
14 [posted](https://mta.openssl.org/pipermail/openssl-project/2021-October/002764.html)
18 fully functional QUIC implementation over a series of releases (2-3).
42 non-goal of the initial release). Our expectation is that other libraries will
52 part of this activity - we can change major release numbers even if APIs remain
56 is a non-goal.
63 1. [Cloudfare](https://cloudflare-quic.com/)
67 ### Non-QUIC OpenSSL Requirements
79 --------------------------
82 [blog post](https://www.openssl.org/blog/blog/2021/11/25/openssl-update/) which
115 of applications ranging from simple single stream clients up to optimised high
116 performance servers
119 -----------------------
131 stream QUIC easily. More likely to want to do multi-stream.
133 * High performance applications (primarily server based) using existing libssl
134 APIs; using custom network interaction BIOs in order to get the best performance
136 using fibres). Would prefer to use the existing APIs - they don’t want to throw
143 ------------------
149 level - the structure of the application should be the same. At runtime
160 * QUIC performance should be comparable (in some future release - not MVP) with
184 ----------------------