Return-Path: 
 <dev-return-30895-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-dev-archive@httpd.apache.org
Received: (qmail 10324 invoked by uid 500); 19 Jun 2002 20:27:26 -0000
Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
list-help: <mailto:dev-help@httpd.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@httpd.apache.org>
list-post: <mailto:dev@httpd.apache.org>
Delivered-To: mailing list dev@httpd.apache.org
Received: (qmail 10311 invoked from network); 19 Jun 2002 20:27:26 -0000
X-Authentication-Warning: mako.covalent.net: dougm owned process doing -bs
Date: Wed, 19 Jun 2002 13:15:11 -0700 (PDT)
From: Doug MacEachern <dougm@covalent.net>
To: <dev@httpd.apache.org>
Subject: mod_unique_id not thread safe
Message-ID: <Pine.LNX.4.33.0206191309490.1248-100000@mako.covalent.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

sooo, since apr_uuid is not thread safe, i figured i could just use 
mod_unique_id.  alas it is not thread safe either.  i know this has come 
up before, but see nothing in the STATUS.  anyone have plans/ideas to fix
mod_unique_id ?  or will mod_unique_id just be changed to apr_uuid once it 
is threadsafe?