On Tue, Jul 7, 2009 at 9:39 AM, Paul Querna <p...@querna.org> wrote: > On Tue, Jul 7, 2009 at 8:39 AM, Graham Leggett<minf...@sharp.fm> wrote: > > Paul Querna wrote: > > > >> Nah, 90% of what is done in moduels today should be out of process aka > >> in FastCGI.... or another method, but out of process. (regardless of > >> MPM) > > > > You're just moving the problem from one server to another, the problem > > remains unsolved. Whether the code runs within httpd space, or fastcgi > > space, the code still needs to run, and if it's written badly, the code > > will still leak/crash, and you still have to cater for it. > > Yes, but in a separate process it has fault isolation.. and we can > restart it when it fails, neither of which are true for modules using > the in-process API directly -- look at the reliability of QMail, or > the newer architecture of Google's Chrome, they are both great > examples of fault isolation. >
Also, it simplifies the programming problem by reducing the number of separate memory and concurrency models that must be accommodated by the application-level code.
