I'd like to replace mod_cgi with mod_cgid in order to avoid an annoying
bug which is in the former but not the latter. What would be the
drawbacks (if any) of doing this? I noticed the following sentence in
http://httpd.apache.org/docs/2.0/mpm.html:
For example, sites that need a great deal of scalability can choose
to use a
threaded MPM like |worker
<http://httpd.apache.org/docs/2.0/mod/worker.html>|, while sites
requiring stability or compatibility with
older software can use a |prefork
<http://httpd.apache.org/docs/2.0/mod/prefork.html>|.
Does this imply (as it seems to) that the MPM approach is not stable?
Any other pitfalls to watch out for? This would be on a
single-processor (AMD64) machine.
Thanks!
--
Bob Kline
http://www.rksystems.com
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
