Lines Matching +full:multi +full:- +full:functional

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).
33   The fully functional release will provide the ability to plug in more
42   non-goal of the initial release). Our expectation is that other libraries will
46 * Once we have a fully functional QUIC implementation (in a subsequent release),
51   functional QUIC release (this does not imply we expect API breakage to occur as
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
119 -----------------------
131   stream QUIC easily. More likely to want to do multi-stream.
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
152 * It shouldn’t be harder to do single stream just because multi stream as a
160 * QUIC performance should be comparable (in some future release - not MVP) with
184 ----------------------