> assuming slow backends My workload isn't so much backends slowly and steadily producing data on each connection, but significantly long pauses before delivering any content at all. The "slow" vs "paused" backend seems more applicable to something like a PHP backend without a View/Presentation tier (as in MVC).
> 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? I would think any such backend should forward the response body (or complete request without a body) as soon as it comes in, streaming if the content is large enough (ex. a PDF). If I desired to buffer all the data before sending to clients (not applicable to me, but I can imagine some use cases), that would be the job of a separate module sitting on the output filter chain, wouldn't it? Rick Houser Web Administration (517)367-3516 > -----Original Message----- > From: Jim Jagielski [mailto:j...@jagunet.com] > Sent: Thursday, December 03, 2015 4:42 PM > To: dev@httpd.apache.org > Subject: Re: reverse proxy wishlist > > 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.hou...@jackson.com> > wrote: > > > > 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. > > > > > > Rick Houser > > Web Administration > > (517)367-3516 > > > > > >> -----Original Message----- > >> From: Plüm, Rüdiger, Vodafone Group > [mailto:ruediger.pl...@vodafone.com] > >> Sent: Thursday, December 03, 2015 10:50 AM > >> To: dev@httpd.apache.org > >> Subject: AW: reverse proxy wishlist > >> > >> How about an async proxy that frees up the thread while waiting on a slow > >> backend? > >> > >> Regards > >> > >> Rüdiger > >> > >>> -----Ursprüngliche Nachricht----- > >>> Von: Jim Jagielski [mailto:j...@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.
