On Fri, Jul 20, 2012 at 12:26 PM, Steinar H. Gunderson <se...@samfundet.no> wrote: > On Thu, Jul 19, 2012 at 06:54:56PM +0100, Tim Bannister wrote: >> I think there's a case for leaving itk separate, a bit like mod_fcgid. It >> is a bit unusual and troubleshooting won't be straightforward. > > Why would you keep mpm-itk separate but mod_privileges not?
IMO it is not a very relevant question given the big picture: * Most modules written for httpd are not bundled with the server or otherwise hosted/developed at the ASF. * mod_privileges is for a minority server operating system and is not used extensively even there. * You won't find much rhyme or reason to why some modules are bundled and some are not other than whether or the author has commit access, and even then there isn't much consistency. As far as mpm-itk: A few hooks can be added to httpd core so that it can be enabled just like other modules*, whether or not anyone here cares about the implementation details. *Of course that isn't really true of the popular 2.2.x branch, but I don't think it is realistic to hope that mpm-itk would ever make it to 2.2.x anyway. By the way, did any other httpd-ers have a look at those patches and have suggestions for what hooks could be added?
