Matthew Byng-Maddick wrote:
This is (in my mind) currently the most broken bit of modperl, because of
the hacks you have to do to make it work. With a proper API for content
filtering (apache2), it will be fantastically clean, but at the moment... :-(
The hacks are getting neater, but yes,
Matthew Byng-Maddick wrote:
[useful description snipped]
Obviously, if your modperl is URL dependent, then you can't determine what
URL they are going to ask for at the time you have to call accept. The only
alternative way of doing what you're asking for is to use file descriptor
passing,
Stas Bekman wrote:
On Tue, 19 Jun 2001, Keith G. Murphy wrote:
Matthew Byng-Maddick wrote:
On Mon, Jun 18, 2001 at 10:41:50AM -0500, Keith G. Murphy wrote:
This is only true if you're serving images off the mod_perl server which
is crazy unless you're generating them.
No
On Tue, 19 Jun 2001, Keith G. Murphy wrote:
Matthew Byng-Maddick wrote:
On Mon, Jun 18, 2001 at 10:41:50AM -0500, Keith G. Murphy wrote:
This is only true if you're serving images off the mod_perl server which
is crazy unless you're generating them.
No images involved, but I was
Stas Bekman wrote:
On Mon, 18 Jun 2001, Keith G. Murphy wrote:
Trevor Phillips wrote:
Is there any way to control which daemon handles a certain request with apache
1.x?
eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
application to 10 specific
Matthew Byng-Maddick wrote:
On Mon, Jun 18, 2001 at 10:41:50AM -0500, Keith G. Murphy wrote:
Trevor Phillips wrote:
Is there any way to control which daemon handles a certain request with apache
1.x?
eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
Gunther Birznieks wrote:
Yeah, just use the mod_proxy model and then proxy to different mod_perl
backend servers based on the URL itself.
Isn't this pretty much what I said is *a* solution?
I suppose I could do this now by having a front-end proxy, and mini-Apache
configs for each group I
At 02:29 PM 6/18/2001 +0800, Trevor Phillips wrote:
Gunther Birznieks wrote:
I suppose I could do this now by having a front-end proxy, and mini-Apache
configs for each group I want, but that seems to be going too far
(at this
stage), especially if the functionality already exists to do
On Mon, Jun 18, 2001 at 02:29:18PM +0800, Trevor Phillips wrote:
Gunther Birznieks wrote:
[Trevor wrote:]
Yeah, just use the mod_proxy model and then proxy to different mod_perl
backend servers based on the URL itself.
Isn't this pretty much what I said is *a* solution?
Yes, and the only one.
I
Trevor Phillips wrote:
Is there any way to control which daemon handles a certain request with apache
1.x?
eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
application to 10 specific daemons would improve the efficiency of data cached
in those processes.
On Mon, 18 Jun 2001, Keith G. Murphy wrote:
Trevor Phillips wrote:
Is there any way to control which daemon handles a certain request with apache
1.x?
eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
application to 10 specific daemons would improve the
On Mon, Jun 18, 2001 at 10:41:50AM -0500, Keith G. Murphy wrote:
Trevor Phillips wrote:
Is there any way to control which daemon handles a certain request with apache
1.x?
eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
application to 10 specific daemons would
Although: Stas:
Since keepalive connections will not incur the additional three-way TCP
handshake, turning it off will be kinder to the network.
erm Surely if you turn it *on* you'll be kinder to the network,
because you're not reinitiating the handshake?
[it] refers to
Is there any way to control which daemon handles a certain request with apache
1.x?
eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
application to 10 specific daemons would improve the efficiency of data cached
in those processes.
If this is impossible in Apache 1.x,
Yeah, just use the mod_proxy model and then proxy to different mod_perl
backend servers based on the URL itself.
At 01:17 PM 6/18/2001 +0800, Trevor Phillips wrote:
Is there any way to control which daemon handles a certain request with apache
1.x?
eg; Out of a pool of 50 daemons, restricting
On Mon, 18 Jun 2001, Trevor Phillips wrote:
Is there any way to control which daemon handles a certain request with apache
1.x?
http://perl.apache.org/guide/strategy.html#Running_More_than_One_mod_perl_S
eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
16 matches
Mail list logo
