Re: Client header for connection speed info

At 01:07 PM 3/6/00 , hardie@equinix.com wrote:

>The contrary argument to this is that the end-to-measurements are not
>necessary, because the constraining factor for a very large number of
>cases is the link speed of the client "last mile" (the dial up modem
>speed, dsl throughput, or whatever).  Since the client can be
>configured to know and report that, it can be used as an indicator.
>This is true, but presents a problem where the last mile isn't the
>constraint (true where there are trans-oceanic links are present, for
>example), or where the requestor does not wish to have that constraint
>used as a limiting factor.

What about the client that sits on a saturated 10/100 Mb Ethernet 
subnet?  Where his or her throughput is directly related on how many 
co-workers are at their computers.  BTW, when is this measurement / 
indicator set?  Is it at initial connection time or is it based on the last 
few packets that have been sent?  If it is the later then the indicator is 
a very moving target that might make a server balk, especially if there is 
a persistent connection between the browser and server.


                         Kevin

===========================================================
Kevin J. Dyer				     Draper Laboratory  MS 35
Email: <kdyer@draper.com>		     555 Tech. Sq.
Phone: 617-258-4962			     Cambridge, MA 02139
FAX: 
617-258-2061                                   http://www.draper.com 

---------------------------------------------------------------------------- 
------------------------------------------
	    _/_/_/_/    _/          _/  _/  _/        _/     _/_/_/_/
	   _/      _/   _/_/     _/_/  _/  _/_/     _/   _/
	  _/       _/  _/ _/   _/ _/  _/  _/  _/   _/    _/_/_/
	 _/      _/   _/  _/ _/  _/  _/  _/    _/ _/            _/
	_/_/_/_/   _/    _/    _/  _/  _/        _/  _/_/_/_/
        Data Management & Information Navigation Systems
===========================================================