Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 24 Nov 2002 00:19:18 -0800
Subject: Re: bug in apr_os_thread_current ? 
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
From: Aaron Bannert <aaron@clove.org>
To: dev@apr.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <2147483647.1038091165@localhost>
Message-Id: <6D3C77C9-FF85-11D6-9A20-000393B3C494@clove.org>


On Saturday, November 23, 2002, at 10:39  PM, Justin Erenkrantz wrote:

> --On Friday, November 22, 2002 6:51 AM -0600 "William A. Rowe, Jr." 
> <wrowe@apache.org> wrote:
>
>> Agreed that it is a bug.  The question is whether it even makes
>> sense to use the thread handle or thread ID.
>>
>> Who is using apr_os_thread_current() and if so, what are you
>> plugging it into?
>
> FWIW, flood is using it as various locations to provide unique 
> per-process ids (OpenSSL requires unique thread ids in order to be 
> threadsafe).  But, it's not passing them to a native OS call, so the 
> value doesn't really matter.  -- justin

Yeah, and as soon as we come up with something better, we will stop
using it in this way. It was a temporary hack to get a unique integer
for each "farmer".

-aaron