httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [PATCH] mod_proxy Keepalives
Date Sat, 31 Mar 2001 12:37:32 GMT

erratta in previous message...
Not enough coffee yet...

In a message dated 01-03-31 12:19:38 EST, Kiley wrote...

> My concern would really be this...
>  If mod_proxy is not updating req->conn_rec->proxy with connection
>  related info then what happens to other modules in the chain that
>  still expect critical things to be updated in the original req->conn_rec
>  itself? Is req->conn_rec->proxy just a 'read only' placeholder?

What I really meant was...

If mod_proxy IS updating the new req->conn_rec->proxy conn_rec
duplicate instead of the original then what happens to legacy
modules that depend on first-level conn_rec to always hold the
right info even across keep-alives?

Any transport layer module such as mod_throttle absolutely
depends on the original req->conn_rec holding accurate info
across all requests being 'kept alive'.

IBM has rewritten BUFF.C and they have made lots of changes
to the original conn_rec itself. Things like the WIN32 handles
have been eliminated and all the client->fd stuff changed to
client->pfd. Is the addition of this duplicate conn_rec which is 
unaware of the IBM changes to conn_rec going to break IBMHTTPD 
right out of the box?

If it's just some kind of 'read-only' thing for mod_proxy I guess
it's moot but is that what it really is? Just a memory bookmark?

Kevin Kiley

View raw message