Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 87957 invoked by uid 500); 15 Feb 2001 21:10:40 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 87909 invoked from network); 15 Feb 2001 21:10:13 -0000 Date: Thu, 15 Feb 2001 13:10:33 -0800 (PST) From: rbb@covalent.net X-Sender: rbb@koj To: new-httpd@apache.org Subject: Re: cvs commit: httpd-2.0/modules/generators mod_status.c In-Reply-To: <000b01c0978e$76182d20$93c0b0d0@roweclan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > From: "Cliff Woolley" > Sent: Thursday, February 15, 2001 1:36 PM > > > > I guess I won't argue this too loudly if people agree that apr_interval_time_t's > > definition is flexible)... > > It is _NOT_ flexible [your definitions are correct below]. > > > While up_time does represent a value related to time, neither apr_time_t nor > > apr_interval_time_t is strictly appropriate: > > I agree > > > apr_time_t is defined to be a value in microseconds since the epoch... this > > usage meets neither criteria and is clearly not the best choice. > > > > apr_interval_time_t is defined to be a value *in microseconds* that is the > > difference between two apr_time_t's... this usage doesn't meet the first > > criterion in that it's not in microseconds; furthermore, > > apr_interval_time_t's are limited to representing intervals of about 70 > > minutes or so given the number of microseconds that can be represented in 32 > > bits, meaning that apr_interval_time_t's are really only useful for > > representing timeouts which are generally much less than 70 minutes. If we > > choose to be flexible about whether an apr_interval_time_t is in > > microseconds or seconds, then I guess this isn't a big deal... but I'll > > leave that up to you all to argue amongst yourselves. =-) > > +/- 35 minutes or so, your 70 minutes is based on an unsigned, which this isn't. > > I will _veto_ any abuse of apr_interval_time_t or apr_time_t in a manner that isn't > consistent with the definitions you cited above. Guys, we have a time value that doesn't fit as either of these. Either we need ANOTHER time type, or we have done something wrong. Please do not tell me: apr_time_t - apr_time_t != (apr_time_t | apr_interval_time_t) Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------