Lines Matching refs:session

844 1. Users who manually inspect parts of the current session through
847 2. Users of session resumption who query the current session
900 to configure a custom session cache implementation different
903 Those users will need to modify the API of their session cache
905 session IDs and values being instances of `mbedtls_ssl_session`:
911                                      mbedtls_ssl_session *session );
915                                      const mbedtls_ssl_session *session );
919 onwards, portable session cache implementations must not access fields of
921 find themselves unable to migrate their session cache functionality without
979   the same session. This use of `mbedtls_ssl_get_session()`
981   * If the various session copies are later loaded into
984     load the same session into different contexts via
986     makes a copy of the session that's being loaded, this
988   * If the various session copies are later serialized
990     the session only once via `mbedtls_ssl_get_session()` and