Lines Matching full:api

4 The OpenSSL project from time to time must evolve its public API surface in
6 occurs, the changes to OpenSSL's public API must be planned, discussed and
8 proposed API change is how a broad spectrum of real-world OpenSSL applications
12 codebases using OpenSSL to remain current with best practices for OpenSSL API
17 anticipate the impact of any evolution of its API on those codebases. This
18 directory seeks to maintain a set of **API usage demos** which demonstrate a
20 This allows the project to discuss any proposed API changes in terms of the
23 this ensures that API evolution is made both with reference to real-world API
27 useful both to current and any future proposed API changes. The set of demos may
29 a present body of understanding of API usage patterns, which can be used to plan
30 API changes.
32 For further background information on the premise of this approach, see [API
45 connections for use with libssl. The libssl API as a whole has a much larger
60 applications to determine libssl API usage patterns. The commonly occurring usage
110 ….c) | S-BIOc | A `BIO_s_connect`-based blocking example demonstrating exemplary OpenSSL API usage |
111 … `BIO_s_connect`-based nonblocking example demonstrating exemplary OpenSSL API usage, with use of …
112 …F | A `SSL_set_fd`-based blocking example demonstrating real-world OpenSSL API usage (correspondin…
113 …A `SSL_set_fd`-based non-blocking example demonstrating real-world OpenSSL API usage (correspondin…