Received: by taz.hyperreal.com (8.6.12/8.6.5) id JAA29711; Thu, 25 Apr 1996 09:32:26 -0700 Received: from epprod.elsevier.co.uk by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id JAA29698; Thu, 25 Apr 1996 09:32:22 -0700 Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by epprod.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id RAA09029 for ; Thu, 25 Apr 1996 17:31:39 +0100 Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Thu, 25 Apr 1996 17:31:10 +0100 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id RAA01660 for new-httpd@hyperreal.com; Thu, 25 Apr 1996 17:31:09 +0100 From: Paul Richards Message-Id: <199604251631.RAA01660@cadair.elsevier.co.uk> Subject: Re: API version #define To: new-httpd@hyperreal.com Date: Thu, 25 Apr 1996 17:31:09 +0100 (BST) In-Reply-To: <199604251559.AA067767986@ooo.lanl.gov> from "Rob Hartill" at Apr 25, 96 09:59:45 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 644 Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com In reply to Rob Hartill who said > > > > > > #define APACHE_NEWAPI 1 > > > > Uh, let's make this real and do something like > > > > #define APACHE_API 1.1 > > Shouldn't the API have its own version number if it undergoes > significant changes? > > It's not obvious looking at a module that requires 1.1 if that'll > work for 1.1.9 or 1.6 yeah, the API should have a version number, it's the same principle as shared libraries. -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155