Return-Path: 
 <dev-return-6784-apmail-apr-dev-archive=apr.apache.org@apr.apache.org>
Delivered-To: apmail-apr-dev-archive@apr.apache.org
Received: (qmail 90938 invoked by uid 500); 19 Jun 2002 16:51:00 -0000
Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:dev@apr.apache.org>
List-Help: <mailto:dev-help@apr.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@apr.apache.org>
List-Subscribe: <mailto:dev-subscribe@apr.apache.org>
Delivered-To: mailing list dev@apr.apache.org
Received: (qmail 90886 invoked from network); 19 Jun 2002 16:51:00 -0000
X-Authentication-Warning: mako.covalent.net: dougm owned process doing -bs
Date: Wed, 19 Jun 2002 09:39:08 -0700 (PDT)
From: Doug MacEachern <dougm@covalent.net>
To: <dev@apr.apache.org>
Subject: apr_uuid is not thread safe
Message-ID: <Pine.LNX.4.33.0206190938160.1285-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


static void get_current_time(apr_uint64_t *timestamp)
{
    /* ### this needs to be made thread-safe! */

    apr_uint64_t time_now;
    static apr_uint64_t time_last = 0;
    static int fudge = 0;

any plans/thoughts on making it threadsafe?