On Wed, 25 Feb 2004, Ged Haywood wrote:
> On Wed, 25 Feb 2004, Richard F. Rebel wrote:
>
> > I would be interested if anyone knows of a mod_proxy replacement
> > that does this sort of multiplexing
>
> I had an idea that mod_accel would do that, but it's been a while
> so I could be completely w
Hi there,
On Wed, 25 Feb 2004, Richard F. Rebel wrote:
> I would be interested if anyone knows of a mod_proxy replacement
> that does this sort of multiplexing
I had an idea that mod_accel would do that, but it's been a while
so I could be completely wrong.
73,
Ged.
--
Report problems: http:/
On Wed, 2004-02-25 at 15:26, Stas Bekman wrote:
> > My question is, should this be the case? We have keepalives disabled on
> > the externally accessible ap2+mp2 intentionally. Is there any benefit
> > or detriment for using them between the two apaches? I would think that
> > keepalives should
Perrin Harkins wrote:
On Wed, 2004-02-25 at 15:26, Stas Bekman wrote:
I remember Theo has mentioned that I think with some of the related to Spread
(spread.org) products. But I don't remember which.
You're thinking of mod_backhand, which doesn't support apache2.
Thank you, precious! I need a me
On Wed, 2004-02-25 at 15:26, Stas Bekman wrote:
> I remember Theo has mentioned that I think with some of the related to Spread
> (spread.org) products. But I don't remember which.
You're thinking of mod_backhand, which doesn't support apache2.
- Perrin
--
Report problems: http://perl.apache.
Richard F. Rebel wrote:
Hello,
Due to about 200,000 lines of legacy mod_perl code that is written for
MP1 and Apache::Request, In order to migrate to mod_perl2 app by app, we
have set up a reverse proxy on the same machines.
All mp2 apps run on the main ap2+mp2, any request for a legacy app is
pro
On Wed, 2004-02-25 at 15:15, Richard F. Rebel wrote:
> I would think that
> keepalives should be off so that the ap1 instances can be freed to
> service another request while the reverse proxy is busy feeding slower
> clients.
And you would be correct!
- Perrin
--
Report problems: http://perl.