Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
From: "Houser, Rick" <rick.houser@jackson.com>
To: "dev@httpd.apache.org" <dev@httpd.apache.org>
Subject: RE: reverse proxy wishlist
Thread-Topic: reverse proxy wishlist
Thread-Index: AQHRLdsvM4DomsTpDEyZS7B3OcNp8p65vMGA///IuGA=
Date: Thu, 3 Dec 2015 17:36:33 +0000
Message-ID: 
 <a138da8b6df34d42a588f5a729ede044@DC01PXMBP007.jacksonnational.com>
References: <288293CD-6D82-42E0-BFC9-9DC25F969ED6@jaguNET.com>
 <AB1691BE05AE7F4992697F2A0835627AC63B8989@VOEXM10W.internal.vodafone.com>
In-Reply-To: 
 <AB1691BE05AE7F4992697F2A0835627AC63B8989@VOEXM10W.internal.vodafone.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

An async mod_proxy backend would be huge for my workloads.  In the JEE spac=
e I deal with, much more time is spent waiting on the application backends =
then with the clients, especially now that we have the event mpm.  Somethin=
g like this would allow me to drastically reduce thread counts and free up =
a lot of associated memory.


Rick Houser
Web Administration
(517)367-3516


> -----Original Message-----
> From: Pl=FCm, R=FCdiger, Vodafone Group [mailto:ruediger.pluem@vodafone.c=
om]
> Sent: Thursday, December 03, 2015 10:50 AM
> To: dev@httpd.apache.org
> Subject: AW: reverse proxy wishlist
>=20
> How about an async proxy that frees up the thread while waiting on a slow
> backend?
>=20
> Regards
>=20
> R=FCdiger
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: Jim Jagielski [mailto:jim@jaguNET.com]
> > Gesendet: Donnerstag, 3. Dezember 2015 15:59
> > An: httpd <dev@httpd.apache.org>
> > Betreff: reverse proxy wishlist
> >
> > I put out a call on Twitter regarding this, but wanted to
> > close the loop here as well.
> >
> > What would *you* like to see as new features or enhancements
> > w/ mod_proxy, esp reverse proxy. I was thinking about some
> > sort of active backend monitoring, utilizing watchdog, which
> > could also maybe, eventually, pull in performance and load
> > data for the backend for a more accurate LB provider. But
> > what about new LB methods? Any ideas there?
> >
> > tia.