Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 4 Aug 2002 15:05:48 -0700
From: Aaron Bannert <aaron@clove.org>
To: dev@apr.apache.org
Subject: Re: cvs commit: apr/time/win32 time.c
Message-ID: <20020804220548.GW26485@clove.org>
Mail-Followup-To: Aaron Bannert <aaron@clove.org>, dev@apr.apache.org
References: <20020804182934.56249.qmail@icarus.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020804182934.56249.qmail@icarus.apache.org>
User-Agent: Mutt/1.4i

On Sun, Aug 04, 2002 at 06:29:34PM -0000, wrowe@apache.org wrote:
> wrowe       2002/08/04 11:29:33
> 
>   Modified:    include  apr_time.h
>                time/unix time.c
>                time/win32 time.c
>   Log:
>     Time in exact ms intervals can be very useful in benchmarking... this
>     patch defines a general API for doing so if the platform supports
>     toggling the clock resolution.  Don't recommend doing so for HTTPD,
>     but flood and ab should appreciate it.

If APR can't guarantee a certain precision across the board, how will
that API be useful?

Also, I'm curious how this works, if you happen to have some
references to docs about how this works on NT, I'd be interested.

-aaron