On Thu, 1 Feb 2001, Daniel Sully wrote: > server. It handles failover from dead app instances, however not very > well, and is a big pile of C code. It also has problems in that because > Apache is not multithreaded, one child copy of that adaptor that has > marked an app instance as dead can't let another child know about that > dead instance. You could use an IPC or DBM file (assuming you have 1 apache machine) to communicate this info. With multiple webservers, you'd need a database or NFS or something. -dave /*================== www.urth.org We await the New Sun ==================*/
- Using modperl as an 'adaptor' front end to an app server... Daniel Sully
- Re: Using modperl as an 'adaptor' front end to an a... Gunther Birznieks
- Re: Using modperl as an 'adaptor' front end to ... G.W. Haywood
- Re: Using modperl as an 'adaptor' front end to ... Martin Wood
- Re: Using modperl as an 'adaptor' front end to an a... Dave Rolsky
- Re: Using modperl as an 'adaptor' front end to ... Daniel Sully
- Re: Using modperl as an 'adaptor' front end... Dave Rolsky
- Re: Using modperl as an 'adaptor' front... Daniel Sully
- Re: Using modperl as an 'adaptor' front end to an a... kyle dawkins
- Re: Using modperl as an 'adaptor' front end to ... Daniel Sully
- Re: Using modperl as an 'adaptor' front end... Kyle Dawkins