[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnutls-dev] Re: living without global variables
From: |
Bryan Henderson |
Subject: |
Re: [gnutls-dev] Re: living without global variables |
Date: |
3 Jan 2006 01:32:40 +0000 |
>The proper way for other
>libraries to use libgcrypt is by wrapping this init function and to
>allow the caller to actually initialize Libgcrypt (hidden in a
>wrapper function).
>
>Unfortunately gnutls does not do this.
Doesn't it? gnutls' global init function does _something_ with
Libgcrypt. How is that different?
>In fact Libgcrypt should never be unloaded but kept in memory for the
>lifetime of the process.
I'm sure you have reasons for this belief, which is essentially that
modularity is not appropriate where Libgcrypt is involved, but it would
be nice if a user had a choice over this policy.
>the only way to make
>Libgcrypt thread safe is by delegating the initialization to the
>actual application - only the application knows what threading model
>it is going to use.
Assuming you have to have global variables, of course.
--
Bryan Henderson Phone 408-621-2000
San Jose, California
[gnutls-dev] Re: living without global variables, Simon Josefsson, 2006/01/09