Lines Matching +full:application +full:- +full:specific

9 -------------------------
14 [posted](https://mta.openssl.org/pipermail/openssl-project/2021-October/002764.html)
15 and that were specific to QUIC
18   fully functional QUIC implementation over a series of releases (2-3).
28 * The application must have the ability to be in control of the event loop without
29   requiring callbacks to process the various events. An application must also have
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
102   application usage to support the full capabilities of QUIC.
119 -----------------------
123 There are different types of application that we need to cater for:
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
158 * Application authors will need good documentation, demos, examples etc.
160 * QUIC performance should be comparable (in some future release - not MVP) with
162   b) application data throughput (bytes per second) for a single stream/connection
167   A single copy API would make it possible for application data being sent or
172   Single copy for sending data occurs when the application supplies a buffer of
180   available to (or supplied by) the application with no further internal copies
184 ----------------------
186 This section summarises those requirements from the above that are specific to