Greg Stein wrote:
> 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.
Ok - makes sense.
> 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.
Using a conn_rec for an outbound connection has allowed us to use
filters - which has cut down the proxy code by an enormous amount.
Outbound connections are almost identical to inbound ones - once the
status or request lines have been removed both outbound and inbound
requests are virtually the same.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
