On 09 Jun 2015, at 3:37 PM, Stefan Eissing <[email protected]> wrote:
> My understanding is that one uses mpm_prefork when threads are to be avoided. > This is not what mod_h2 is about and so I consider disabling the module in a > prefork configuration. My thinking: if threads are not a problem, why not run > worker/event? Getting prefork to work would be a good thing. The prefork MPM is the “tank” MPM - regardless of what the client does, regardless of what code is being spawned by httpd, any leak/crash affects that connection only. mod_h2 might not be fully featured or fully performant under prefork, but that’s fine in theory. Regards, Graham —
