Ruediger Pluem wrote:
Then you can easily just use
<Proxy ajp://localhost:8009>
ProxySet ...
</Proxy>
It will define a 'known' worker.
There is no need for an additional directive.
Yes, this idea came also up to me after sending the mail.
It seems to be an acceptable solution for this problem, but
we should really add ProxySet to the documentation to make this
more obvious to other people :-).
Sure.
Furthermore I think there should be some hints that mod_rewrite
proxy requests will use the default worker (which has no pooling)
if the worker is not defined explicitly.
You cannot create AJP workers (or any other BTW) on-the-fly.
That's why we have *:* forward and reverse workers.
Although they work with http/ftp/connect protocols they
do not work for constant connection protocols like AJP or
FCGI.
IMHO the solution is to simply not forward the requests
with unknown workers for constant connection protocols.
The reason is that any attempt to cache the workers
would make them immutable between child processes, because
they would be created at request time.
Multiple connection pools per worker might help, but that
solution would also lack the shared memory status data.
Anyhow since those types are not meant for balancer workers
this solution could be actually usable :).
For example, the generic forward worker (only one that
makes sense), would need a protocol:host:port keyed
connection pool table (probably interchangeable with
predefined workers if they exist).
Regards,
Mladen.
