Changeset 6814e48 in mod_gnutls for src


Ignore:
Timestamp:
Jun 5, 2016, 3:42:32 PM (3 years ago)
Author:
Thomas Klute <thomas2.klute@…>
Branches:
debian/master, debian/stretch-backports, master, upstream
Children:
2f932fa
Parents:
15245bf
git-author:
Thomas Klute <thomas2.klute@…> (06/04/16 21:44:14)
git-committer:
Thomas Klute <thomas2.klute@…> (06/05/16 15:42:32)
Message:

Explain the different signatures of the dbm_cache functions

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src/gnutls_cache.c

    r15245bf r6814e48  
    309309#define SSL_DBM_FILE_MODE ( APR_UREAD | APR_UWRITE | APR_GREAD | APR_WREAD )
    310310
     311/***
     312 * The signatures of the dbm_cache_...() functions may be a bit
     313 * confusing: "store" and "expire" take a server_rec, "fetch" an
     314 * mgs_handle_t, and "delete" the void* required for a
     315 * gnutls_db_remove_func. The first three have matching ..._session
     316 * functions to fit their respective GnuTLS session cache signatures.
     317 *
     318 * This is because "store", "expire", and "fetch" are also needed for
     319 * the OCSP cache. Their ..._session variants have been created to
     320 * take care of the session cache specific parts, mainly calculating
     321 * the DB key from the session ID. They have to match the appropriate
     322 * GnuTLS DB function signatures.
     323 *
     324 * To update cached OCSP responses independent of client connections,
     325 * "store" and "expire" have to work without a connection context. On
     326 * the other hand "fetch" does not need to do that, because cached
     327 * OCSP responses will be retrieved for use in client connections.
     328 ***/
     329
    311330static void dbm_cache_expire(server_rec *s)
    312331{
Note: See TracChangeset for help on using the changeset viewer.