MPMs and modules

Is it realistic to expect that a module compiled against Apache using
the worker MPM could be used on an Apache compiled using the prefork
MPM?
Or does the choice of MPM influence the content of the headers that
modules include when compiled?

I suspect that the choice of MPM at compile time only affects the httpd
binary and
possibly the generation of a MPM module.
Therefore it ought to be possible to have a single Apache install with
httpd.prefork and httpd.worker in place of httpd, and depending upon
which I use, get the desired behavior.
Looks like Fedora Core 2 includes an apache that does this.
Anyone disagree?

{{{ Andy

ak@nyangau.fsnet.co.uk wrote:
> Is it realistic to expect that a module compiled against Apache using
> the worker MPM could be used on an Apache compiled using the prefork
> MPM?

In general, yes. Most modules are both source- and binary-compatible
with any MPM. But there could be exceptions to that amongst third-
party modules, and there are some modules that work better with one
MPM than another.

--
Nick Kew