On Fri, 6 Apr 2007 00:51:52 -0400 "Sam Carleton" <[EMAIL PROTECTED]> wrote:
> (for now, assume that the whole > application will be in the apache module.) That assumption seems fundamentally flawed. A substantial and complex application will be built from a number of modules, and is likely to mix preexisting components with new ones. If you're thinking of all your work being one module, then you need to take a step back and review it. A good startingpoint is "one module per task". How many tasks does your application comprise? How many of those tasks can be accomplished using existing modules? It's also of course a valid approach to mix-and-match modules with other components such as scripts and backends. But I guess you see that as an intermediate stage in your work. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/
