Technology, Support, and News Forum

[rippinchikkin]

<img src="http://parcom.pro-networks.org/images/apache.jpg" align="right" alt="A look at Apache modules">A look at Apache modules
By Nick Kew
3rd October 2006 21:03 GMT

As I write this, I'm on the Eurostar train, just returning from O'Reilly's OSCon (Open Source Conference) in Brussels. Some fascinating insights there; and even my own talk generated some interesting discussion. Some of the delegates, including O'Reilly himself, are promoting opensource ideas going beyond software and into society more generally.

I've touched on that in this very column before now, but a related argument that's new to me is that the open/closed debate in software could become largely sidelined, as the industry focuses on software as a service (such as Google's offerings) more than as a product. Anyway, I've been meaning for some time to give you an article on writing Apache modules.

But first things first. If you're going to write modules, you'll need a proper Apache installation. A safe option is to download the latest release version (currently 2.2.3) from httpd.apache.org, and install it from that. For the adventurous, you could install the current development version from svn.apache.org. If you use a different package such as an rpm or deb, you'll probably need an "apache-dev" package as well as Apache itself.

What is a module? As I'm sure I've said, Apache has a diverse developer and user profile, and we all have very different uses for it. This approach to serving a wide range of needs is based on a small core, together with a large number of modules. Most of what you get when you install Apache as a package, from apache.org or elsewhere, comprises the modules that perform Apache's standard functions.

<img src="http://www.pro-networks.org/forum/images/smiles/source.jpg"> The Register
<img src="http://www.pro-networks.org/forum/images/smiles/view.jpg" border="0"> <a href="http://www.regdeveloper.co.uk/2006/10/03/apache_modules/" target="_blank"> complete article</a>