On Fri, Oct 3, 2008 at 3:48 AM, Ruediger Pluem [EMAIL PROTECTED] wrote:
I guess the documentation is wrong. This behaviour was changed a while
ago to the behaviour you describe: If a resource is expired it will not
be handed out any longer but it will be closed. This is needed / useful
e.g.
On 10/03/2008 06:08 AM, peter baer wrote:
Also, if you look at the apr_reslist_create() documentation, it states
that the ttl if non-zero, sets the maximum amount of time a resource
may be available while exceeding the soft limit. . Why then is the
destructor being called for all resources
Hi Bojan,
First, I'd like to say thank you for the quick response. The ttl is in
fact in microseconds. The documentation seems to be incorrect:
apr_memcache_server_create() ttl - time to live in seconds of a client
connection.
Also, if you look at the apr_reslist_create() documentation, it
On Thu, 2008-10-02 at 21:08 -0700, peter baer wrote:
Also, if you look at the apr_reslist_create() documentation, it states
that the ttl if non-zero, sets the maximum amount of time a resource
may be available while exceeding the soft limit. . Why then is the
destructor being called for all
On Wed, 2008-09-10 at 18:38 -0700, peter baer wrote:
This never used to happen on
earlier versions.
Resource list code in memcache changed slightly with 1.3.4 (some memory
leaks were closed).
I have attached a test program (main.c) showing how I triggered this
issue. It has a hard min of 32,
