Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4C72B095.4020005@apache.org>
Date: Mon, 23 Aug 2010 19:32:05 +0200
From: Mladen Turk <mturk@apache.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: dev@apr.apache.org
Subject: Re: Multiple use of apr_initialize,
 apr_pool_create_ex and apr_dbm_open_ex
References: <AANLkTim+TgkjY2ehSHHpeoppAHBLFF4K4+k361Jd7Ygz@mail.gmail.com>
In-Reply-To: <AANLkTim+TgkjY2ehSHHpeoppAHBLFF4K4+k361Jd7Ygz@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 08/23/2010 04:53 PM, Christian K. wrote:
> Hello,
>
>
> In this application I want to write a dbm file, to use for HTTPD
> authentication. Since I do not want to make any assumption on the
> initialization state of apr I would like to repeatedly initialize and
> terminate apr.

IMHO this is API misuse.
It's not a problem if you call apr_initialize or apr_terminate
multiple times, since only the first and last will actually
do the job (although they are not thread safe).
However apr_terminate is meant to be used at process exit
as a top level cleanup.

See:
http://apr.apache.org/docs/apr/1.4/group__apr__library.html

It clearly states that apr_initialize/apr_terminate should be
used as entry and exit point to the *library* (which usually
translates to a single calls per process life time)


Regards
-- 
^TM