On Fri, Mar 7, 2008 at 11:51 AM, Jos Backus <[EMAIL PROTECTED]> wrote:
> Looks like a separate service is used for each Mongrel. Of course that can be > done easily. The solution I'm looking for manages multiple Mongrels under a > single service, just like Apache manages its own worker children. As far as I know, Mongrel doesn't do that -- there's no parent process managing worker children at all; every mongrel is, in effect, an independent peer. I'm not sure of the technical reason for this -- perhaps spawning workers is too expensive (or workers are generally too large) for this to be effective in practice? I was also a bit confused by this at first, having come from the Apache world -- but yeah, I've never seen any solution that didn't involve treating every mongrel as a separate service. Cheers, -Nate _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
