1. Roy has confirmed that idle time and not session time is what is
being timed... Good! Out here where the rubber meets the road it
is quite common for a single document to take more than 1 minute
to receive (with imbeded pieces of course). An that is with wider
pipes than 14.4.
2. As I recall, Jeffery Mogul's data was captured at the server and
roughly represents client to server access. I would postulate
that client-proxy connections will have a very different profile
in that they will almost always be a long runing series of
requests from the client to the proxy. Do we have any data to
look at this part of the protocol's implications?
3. My understanding thus far is that client-proxy and proxy-server
connections are independant of each other in that an efficient
proxy might keep a long connection with each client and use
a pool of long connections to servers to satisfy the client's
requests. In particular, there is no requirement that a
given proxy-server connection be used for a single client.
This raises some interesting issues:
1. Serving from a shared connection may/will have some access
control issues. Similar but not identical to caching
concerns.
2. There seems to be a notion that state information will be
maintained by the server about the connection (is this the
response you were looking for Roy?). I suspect that
a major payback will exist for keeping proxy-server
connections open and shared between the proxy's client.
The rules for keeping state on that connection will need to
be extra carefully thought out. Or perhaps a special
method (RESETSTATE) or header could be used when the proxy
assigns the connection to different client?
Dave Morris