httpd-modules-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Kew <>
Subject Re: Understanding how to write large application in apache modules
Date Mon, 03 Dec 2007 21:58:06 GMT
On Mon, 3 Dec 2007 16:24:47 -0500
"Sam Carleton" <> wrote:

> I am more interested in theory right now than anything else.
> Currently my web development is 80% PHP and 20% Apache Module.  The
> Apache module is currently a handler for my images and controls
> security.

That looks like a valid approach.

> The more I think about it, the more this sounds like what folks are
> doing with input and output filter in Apache modules.  I am starting
> to think that it is possible to develop a whole solution solely as an
> Apache module and simply have it filter HTML template files filling in
> "variables".  Is this how folks do it?

That's a valid approach too, mod_publisher or the XMLNS framework
being examples.

If you feel the urge to change what you've got, I'd start by breaking
down your problem into subtasks.  Then identify good candidates for
implementing as a module, and go ahead and do it.

Your position may be akin to what mine was when I first made apache
modules a core part of my work.  I started by converting input
(form decoding/file upload) and output (XSLT) to filter modules,
then converted some but not all of the applications in the middle.

Nick Kew

Application Development with Apache - the Apache Modules Book

View raw message