Re: Whither mxs? [was: Possible New Optional Field in Header?]

Dan asks:

> Ack! No it doesn't! What happened to the "mxb" parameter?

I assume you mean "mxs".  It is no longer part of HTTP/1.0 because
we determined that there was no reliable way for the server to
estimate the delay for the client.

The client can duplicate the concept of mxs (it was never implemented)
by measuring retrieval time/bytes and sending a dynamically adjusted mxb
which reflects the clients current retrieval rate from that server.


 ....Roy T. Fielding  Department of ICS, University of California, Irvine USA
                                       <fielding@ics.uci.edu>
                      <URL:http://www.ics.uci.edu/dir/grad/Software/fielding>

Received on Wednesday, 10 May 1995 19:22:53 UTC