Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <498E39C5.2040509@sharp.fm>
References: <9338f5ad0902071514k1e834d08rd34264f3084081c8@mail.gmail.com>
	 <498E39C5.2040509@sharp.fm>
Date: Sun, 8 Feb 2009 10:22:47 -0800
Message-ID: <9338f5ad0902081022p744b7982j7ec1937a6b3b257a@mail.gmail.com>
Subject: Re: Getting pool associated with current thread/child
From: Brian McCallister <brianm@skife.org>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Sat, Feb 7, 2009 at 5:47 PM, Graham Leggett <minfrin@sharp.fm> wrote:
> Brian McCallister wrote:
>
>> So, in mod_lua I need to get the apr pool associated with the current
>> thread (that being the main thread if in prefork).
>
> What about the process_rec structure?
>
> In other words, r->server->process->pool?

I thought this was one-per-process, where process is a real process. I
need one-per-thread in in worker/event so that they don't step on each
other.

What I am looking for is to attach a lua_State instance to that pool,
so that when the thread is retired, I can hook into cleanups, and so
that I can attach the lua_State to the pool as userdata, to retrieve
it later.

In prefork, a process level pool would work fine, but AFAIK this is
not a thread-safe thing.

>
> (Not sure if this is what you are looking for, but a quick glance at the
> headers would suggest it probably does).
>
> Regards,
> Graham
> --
>