Re: mod_so/3405: LoadLibrary with relative paths assumes libraries are relative to ap_server_root. (fwd)

[Marc Slemko <ma...@znep.com>]

The following reply was made to PR mod_so/3405; it has been noted by GNATS.

From: Marc Slemko <ma...@znep.com>
To: Apache bugs database <ap...@apache.org>
Cc:  Subject: Re: mod_so/3405: LoadLibrary with relative paths assumes libraries
 are relative to ap_server_root. (fwd)
Date: Mon, 16 Nov 1998 13:25:10 -0800 (PST)

 ---------- Forwarded message ----------
 Date: Mon, 16 Nov 1998 14:49:28 -0500
 From: John Kelly <Jo...@bellhow.com>
 To: marc@apache.org
 Subject: Re: mod_so/3405: LoadLibrary with relative paths assumes libraries are
     relative to ap_server_root.
 
 Marc,
 
 I would like to use static configuration files on all systems where document
 root is a CDROM.  The drive
 letter of the CDROM can be different from system to system and even
 different on the same system with
 multiple CDROMs.  Tying the server root to the support modules appears to be
 arbitrary and not very
 intuitive.  I would like to thing the generic components of Apache could
 reside anywhere and the servlets,
 cgi-bin scripts, etc that are tied to the data are in the server root
 directory.  The current implememtation
 requires each server root to have all the apache components present,
 therefore, one can not simply
 change the server root to point to a new "data set".   Note: the proposal
 did not change the current
 behavior,  but extended it to allow the dlls to reside with apache.exe
 independent of the server root.
 
 This proposal may not conform to the design philosophy of the Apache
 product, however, the current approach arbitarily loads dlls from where
 apache was loaded (ApacheCore.dll) and other dlls from
 DocumentRoot/modules/ such as ApacheModuleJServ.dll which seems to be a
 combination of  "any which directory". The search order of dlls is
 well-documented, although it is magical based upon you current
 directory.
 
 I don't mean to cause a lot of trouble, I already made the change, however,
 I thought others may want to
 perform the same type of thing - switching between multiple "data sets"
 without requiring all the apache
 components to be available on each one.  This was just an attempt at
 providing some useful feedback
 on the Apache product.  You can take it or leave it.
 
 John.
 
 
 
 -----Original Message-----
 From: marc@apache.org <ma...@apache.org>
 To: apache-bugdb@apache.org <ap...@apache.org>;
 john.kelly@bellhow.com <jo...@bellhow.com>; marc@apache.org
 <ma...@apache.org>
 Date: Monday, November 16, 1998 12:13 PM
 Subject: Re: mod_so/3405: LoadLibrary with relative paths assumes libraries
 are relative to ap_server_root.
 
 
 >[In order for any reply to be added to the PR database, ]
 >[you need to include <ap...@Apache.Org> in the Cc line ]
 >[and leave the subject line UNCHANGED.  This is not done]
 >[automatically because of the potential for mail loops. ]
 >[If you do not include this Cc, your reply may be ig-   ]
 >[nored unless you are responding to an explicit request ]
 >[from a developer.                                      ]
 >[Reply only with text; DO NOT SEND ATTACHMENTS!         ]
 >
 >
 >Synopsis: LoadLibrary with relative paths assumes libraries are relative to
 ap_server_root.
 >
 >State-Changed-From-To: open-feedback
 >State-Changed-By: marc
 >State-Changed-When: Mon Nov 16 09:12:12 PST 1998
 >State-Changed-Why:
 >Magically looking for DLLs in any which directory is bad.
 >We want to avoid that.
 >
 >Why don't you just give the proper path to it in the
 >LoadModule line?  That works fine for me.
 >
 >