-1 on the conn_rec patch.
Use conn_config if you want to store more things in there.
On Sat, Mar 31, 2001 at 03:05:32PM -0500, [EMAIL PROTECTED] wrote:
>...
> Isn't the actual proxy target tied to config or Virtual Host dirs?
> Why not add a conn_rec to the actual config info which is
> also persistent across connections? I like the idea of adding
> 'target' connection info to client conn_rec but if mod_proxy
> can just refer to it's config info for target connection stuff
> then is the new item in conn_rec really needed?
This is the Right Way to solve it. The proxy should hold a pool of
connections to other servers. When a request comes in, it looks in the pool
for an available connection, pulls it from the pool (so it won't get used by
two requests simultaneously), runs the request with it, if the connection
remains open, then puts it back in the pool.
Tying the outbound connections to incoming connections isn't Right.
Further, using a conn_rec for an *outbound* connection is just wrong. Yes,
there is a tiny bit of similarity. But things like base_server,
vhost_lookup_data, remote_logname, double_reverse, local_ip, local_host, etc
... none of those apply whatsoever to outbound connections.
It is confusing to use conn_rec for outbound connections. The semantic is
wrong. Design a new structure instead.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
