Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: reverse proxy wishlist
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: 
 <a138da8b6df34d42a588f5a729ede044@DC01PXMBP007.jacksonnational.com>
Date: Thu, 3 Dec 2015 16:42:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BCAF888-2CF5-4965-A644-C42B3211F6BC@jaguNET.com>
References: <288293CD-6D82-42E0-BFC9-9DC25F969ED6@jaguNET.com>
 <AB1691BE05AE7F4992697F2A0835627AC63B8989@VOEXM10W.internal.vodafone.com>
 <a138da8b6df34d42a588f5a729ede044@DC01PXMBP007.jacksonnational.com>
To: dev@httpd.apache.org

Thx! assuming slow backends, how would you like httpd to
handle it: should it just slurp in the data from the backend
and buffer it and send it to the client all in one go? Should
it instead forward data as soon as it gets it?
> On Dec 3, 2015, at 12:36 PM, Houser, Rick <rick.houser@jackson.com> =
wrote:
>=20
> An async mod_proxy backend would be huge for my workloads.  In the JEE =
space 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.  Something like this would allow me to drastically reduce thread =
counts and free up a lot of associated memory.
>=20
>=20
> Rick Houser
> Web Administration
> (517)367-3516
>=20
>=20
>> -----Original Message-----
>> From: Pl=FCm, R=FCdiger, Vodafone Group =
[mailto:ruediger.pluem@vodafone.com]
>> 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
>>>=20
>>> I put out a call on Twitter regarding this, but wanted to
>>> close the loop here as well.
>>>=20
>>> 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?
>>>=20
>>> tia.