perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gunther Birznieks <>
Subject Re: Using modperl as an 'adaptor' front end to an app server.
Date Fri, 02 Feb 2001 10:44:07 GMT
Yes, we do this for several clients using SOAP as an RPC transport to Java 

I think you could pretty easily just use socket timeout setting to say that 
if you don't get a response back within a period of time that you fail over 
to another server.

The downside for SOAP is that the connection is not a persistent socket. 
SOAP is a protocol running over HTTP so you may find it slower than 
sockets. However, for many applications it's fast enough.

I've also used PL/RPC, but I can't say that I was very happy with the 
stability of the PL/RPC server but that was over a year ago. And it could 
have been due to some XS modules that were persistent in the PL/RPC server.

Anyway, you should be able to implement your own custom handler to talk 
your proprietary socket protocol in mod_perl.


At 10:28 PM 2/1/2001 -0800, Daniel Sully wrote:
>Is anyone using modperl in a way that it acts as an adaptor/scheduler in
>front of an app server in a 3-tier application environment?
>Basically I have a vendor provided (with source however) adaptor that
>takes incoming requests to the webserver, and passes that request onto
>an any number of applications via a socket running on a different
>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.
>Before I reinvent this C wheel in modperl, has anyone done so already?
>Off the record, on the QT, and very hush-hush.

Gunther Birznieks (
eXtropia - The Web Technology Company

View raw message