With the 'MaxRequestsPerChild' setting to 1 this seems to be fairly
effective. I am not running into any of these issues I ran into before with
namespace collision. I am not sure how this would scale for larger teams
( 20+ developers ) but it will do for our environment.
> I also thought about configuring the apache server differently on
> development so that child processes get recycled much faster than on
> production so as to allow for each request to use it's own
> memory. This can
> be resource intensive but again it would only be on development. Also,
> packages/modules will need to be called on a per request basis in
> development.
>
> I will let you know if it is feasible.
>
> Thanks,
>
> > I agree. I've seen many people try to do shared memory/cached
> programming
> > in one server and it just doesn't work very well in practice. It
> > only takes
> > one programmer a typo to take everyone else down until the bug is fixed.
> >
> > From Jakarta/Tomcat to IIS to Apache/mod_perl. Developers having
> > their own
> > workstation is the best for testing and active development. Of course, a
> > staging server needs to be shared. But it's a lot cleaner once the
> > developer has debugged their own code.
> >
>
>
