Yo ho ho
> > However, it wasn't a full implementation of the adaptor and didn't work
with
> > KeepAlive requests and so forth.
>
> Hmm.. given the source to the adaptor, and being able to turn debugging
> on, it looks pretty simple.
Absolutely... we'd need to sift thru the adaptor source and pie
Once upon a time Dave Rolsky shaped the electrons to say...
> > That would be a no. Socket communication only. Shared filesystems in
> > production are bad, mmkay.
>
> I'm not sure which you're referring to, my suggestion that you use a DBM
> file (with locking, of course) on 1 machine or NFS.
On Fri, 2 Feb 2001, Daniel Sully wrote:
> > 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.
>
> That would be a no. Socket communication only. Shared filesystems in
> prod
Once upon a time kyle dawkins shaped the electrons to say...
> A wild guess here but are you talking about WebObjects?
Yes - I've hacked up the WO 4.5 adaptor pretty bad, and it's a pile already.
> I wrote a perl adaptor last year to sniff the traffic that the WebObjects
> adaptor was sending
Once upon a time Dave Rolsky shaped the electrons to say...
> 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
Daniel
A wild guess here but are you talking about WebObjects?
On Fri, 02 Feb 2001 01:28, 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?
I wrote a perl adaptor last year to sniff the tr
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 l
On Fri, Feb 02, 2001 at 06:44:07PM +0800, Gunther Birznieks wrote:
> Yes, we do this for several clients using SOAP as an RPC transport to Java
> middleware.
Out of interest, are all these clients using different SOAP implementations on
different platforms?
We are designing a system that acce
Hi all,
On Fri, 2 Feb 2001, Gunther Birznieks wrote:
> Anyway, you should be able to implement your own custom handler to talk
> your proprietary socket protocol in mod_perl.
I did this last year for a Client in the Big Smoke. Only about twenty lines.
Sorry, can't give a way any source - it's
Yes, we do this for several clients using SOAP as an RPC transport to Java
middleware.
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 c
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 applic
11 matches
Mail list logo
