[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
Synopsis: MODULE_MAGIC_NUMBER checking makes distributing modules in binary form nearly impossible State-Changed-From-To: open-closed State-Changed-By: akosut State-Changed-When: Mon Jul 27 09:38:25 PDT 1998 State-Changed-Why: This is in fact an intended feature of the MODULE_MAGIC_NUMBER check. Apache 1.x has not been designed with binary compatibility in mind, and were this check not present, all manner of horrors would be unleashed if modules compiled agaist different versions of Apache were linked together. In fact, nearly every MODULE_MAGIC_NUMBER change (see http://dev.apache.org/mmn.txt for a partial list) in 1.3 development cycle is a change that breaks binary compatibility. Regardless of whether the check was bypassed, modules simply wouldn't work. It should be pointed out that this is only a problem during beta cycles, and we do not reccomend distributing binary modules for beta software. The API of final Apache releases are quite stable; All 1.2.x versions share the same MODULE_MAGIC_NUMBER, for example. We expect that modules compiled for 1.3.1 will be linkable with Apache 1.3.x for many months to come. However, you do bring up a good point, and it establishing methods of maintaining binary backwards-compatibility for modules is a priority for Apache 2.0. Thanks for using Apache.
