the Apache HTTP Server 2.0.x version.
Thomas
-Original Message-
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 10:51 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Apache HTTP Server 2.0.55 Windows install
.dll, .so, .ocx, .cpl, .scr, .
ailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 10:51 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Apache HTTP Server 2.0.55 Windows install
.dll, .so, .ocx, .cpl, .scr, .nls. They are ALL dynamic libraries, the
filename is irrelevant. It only helps you to distinguish one ty
.dll, .so, .ocx, .cpl, .scr, .nls. They are ALL dynamic libraries, the
filename is irrelevant. It only helps you to distinguish one type of module
from another. So .so is a perfectly logical associate for apache modules.
Apache can only load an 'apache module' - e.g. a module with an exported
F
I installed Apache Win32 Binary (MSI Installer):
apache_2.0.55-win32-x86-no_ssl.msi located at
http://httpd.apache.org/download.cgi. Why are all of the files in the
modules directory *.so files? Aren't those for UNIX? I need to use
mod_jk and was expecting a mod_jk.dll instead.
Thomas
