Quoting Ask Bjørn Hansen ([EMAIL PROTECTED]): > > > Handlers to be run first could be either before others requesting to > run first, or after those? (I was planning to lookup what Apache HTTPD > does and just model after that -- the first, middle, last idea is from > there IIRC).
IIRC, Apache has a sequence of phases that make up a request cycle. These are analogous to the hooks that are in qpsmtpd. Within each phase an apache module (analogous to qpsmtpd's plugins) are allowed to register for one or more phases in the request cycle. For modules written in C, the precedence with which a given module is given within a particular phase is determined by the order in which a module is listed in a data structure determined at compile time. If the module is loaded dynamically, then it's order is the determined by where in the configuration file it is referenced. The same is mostly true for Apache Perl handlers. mod_perl, being a C module, registers itself for all phases of the request cycle and then allows Perl modules to register themselves for a particular phase. The order of execution is again determined by the order of they are listed in the configuration file, but for Perl modules the order can be altered dynamically at runtime as well.
