On 3/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
--- httpd/httpd/trunk/modules/proxy/mod_proxy.c (original)
+++ httpd/httpd/trunk/modules/proxy/mod_proxy.c Thu Mar 9 10:39:16 2006
@@ -218,6 +218,26 @@
}
}
}
+else if (!strcasecmp(key, ajpflushpackets)) {
-Ursprüngliche Nachricht-
von Garrett Rooney
Sticking per-backend info like ajp_flush_wait into the worker
object and the code to configure it in mod_proxy.c itself
seems very wrong to me. There should be a per-backend
contect pointer to hold per-backend information, and the
=?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_VIS?= wrote:
von Garrett Rooney
=20
Sticking per-backend info like ajp_flush_wait into the worker=20
object and the code to configure it in mod_proxy.c itself=20
seems very wrong to me. There should be a per-backend=20
contect pointer to hold
-Ursprüngliche Nachricht-
Von: Jim Jagielski
Agreed. I'm +1 for making it non-AJP specific to handle
the other issues. But I wanted it to crawl before walk :)
Thats a very good idea :-).
Regards
Rüdiger
