Lines Matching full:apis
5 the new and changed APIs, and the design constraints motivating those API
13 + [Existing APIs](#existing-apis)
32 + [New APIs for Single-Stream Operation](#new-apis-for-single-stream-operation)
46 + [New APIs for Multi-Stream Operation](#new-apis-for-multi-stream-operation)
60 + [Future APIs](#future-apis)
62 + [Existing APIs](#existing-apis-1)
67 + [New APIs](#new-apis)
81 A listing of all SSL object APIs and their implications for QUIC, including
85 Non-SSL object APIs which are new or changed, or otherwise discussed in this
87 APIs are not listed here; see [quic-api-ssl-funcs.md](./quic-api-ssl-funcs.md)
88 for details on SSL object APIs.
119 - to reuse the existing libssl APIs to the extent feasible;
167 ### Existing APIs
428 ### New APIs for Single-Stream Operation
867 ### New APIs for Multi-Stream Operation
869 The above new APIs are built on constructively to facilitate multi-stream
884 Initially these APIs will not be thread safe over the same connection, but in
888 multi-thread (MSMT) operation. Only APIs explicitly denoted below will
1175 ### Future APIs
1183 ### Existing APIs
1227 ### New APIs
1238 Unlike all other BIO APIs, this API is intended for concurrent threaded use and
1262 Custom BIO implementers may set their own implementation of these APIs via
1356 for the new APIs `BIO_sendmmsg`, `BIO_recvmmsg`, the capability negotiation