Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 23372 invoked by uid 6000); 4 Mar 1998 13:31:43 -0000 Received: (qmail 23366 invoked from network); 4 Mar 1998 13:31:41 -0000 Received: from ns2.remulak.net (HELO Mail.Golux.Com) (root@198.115.138.27) by taz.hyperreal.org with SMTP; 4 Mar 1998 13:31:41 -0000 Received: from Golux.Com (p5.ts2.nashu.NH.tiac.com [206.119.233.38]) by Mail.Golux.Com (8.8.5/8.8.5) with ESMTP id IAA10281; Wed, 4 Mar 1998 08:30:21 -0500 Message-ID: <34FD57F4.812DAA58@Golux.Com> Date: Wed, 04 Mar 1998 08:32:36 -0500 From: Rodent of Unusual Size Organization: The Apache Group X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: cvs commit: apache-1.3/src/include hide.h References: <199803041216.NAA29359@en1.engelschall.com> <34FD4E41.32D955E1@Golux.Com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org I'll actually go further: I'd like to see the "AP_" prefix changed to "appriv_" (or whatever we decide the httpd-internal prefix should be). If UpdateHide were eventually augmented to pick up a list of formal API names from somewhere, and prefixed them with the "apapi_" prefix, I would be very happy - we'd be well on our way out of this morass of "just what is the API, anyway?" We'd have three categories of names: apapi_xxx for httpd API routines, appriv_xxx for internal httpd routines, and ap_xxx for Apache reusable routines that aren't tied to the HTTP project. Going back and actually renaming the routines could be done at leisure. I consider this an extreme goodness. #ken P-)} Ken Coar Apache Group member "Apache Server for Dummies"