Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 8500 invoked by uid 6000); 9 Feb 1999 00:54:41 -0000 Received: (qmail 8492 invoked from network); 9 Feb 1999 00:54:39 -0000 Received: from smtp.lerdorf.on.ca (HELO sunlab.bellglobal.com) (199.243.250.75) by taz.hyperreal.org with SMTP; 9 Feb 1999 00:54:39 -0000 Received: from collective.lerdorf.on.ca (collective.lerdorf.on.ca [207.164.141.23]) by sunlab.bellglobal.com (8.9.1/8.8.8) with ESMTP id TAA09207 for ; Mon, 8 Feb 1999 19:56:33 -0500 (EST) Date: Mon, 8 Feb 1999 19:54:34 -0500 (Eastern Standard Time) From: Rasmus Lerdorf To: new-httpd@apache.org Subject: Re: Module Magic Number and binary module compatibility In-Reply-To: <008e01be53c6$52de8f60$0502a8c0@blanca.covalent.net> Message-ID: X-X-Sender: rasmus@imap3.bellglobal.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org > I've been trying to get some time looking at the module interface from > a binary module viewpoint. > > It seems that one really simple solution would be to give the decision > to the module as to whether to run based on the compiled in MMN. Does > this not make more sense? The module should have more knowledge about > whether it can deal with the available API and even perhaps accomodate > the differences. Accomodate the difference at run-time? Looking through all the '#if MODULE_MAGIC_NUMBER >= XXX' blocks in the PHP module it could get extremely ugly to do this. But possible, I guess. -Rasmus