[11497] in www-talk@info.cern.ch
Client header for connection speed info
daemon@ATHENA.MIT.EDU (Tam Freestone-Bayes)
Thu Mar 2 13:08:22 2000
Date: Thu, 2 Mar 2000 12:15:34 -0500 (EST)
Old-X-Envelope-From: www-talk-request@tux.w3.org Thu Mar 2 12:15:32 2000
Message-Id: <20000302171459.7251.qmail@hotmail.com>
From: "Tam Freestone-Bayes" <tamagen@hotmail.com>
To: www-talk@w3.org
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Old-X-Envelope-To: www-talk
Resent-From: gerald@w3.org
Resent-To: www-talk@w3.org
Many sites and their users can benefit from the provision of more than one
http interface to a site - for example, the increasingly widespread
bandwidth discrepancy between standard modem and broadband connections may
encourage developers to produce both high- and low-bandwidth versions of a
site.
Many sites implement this but rely on the user to manually select which site
they "prefer".
If the site developer knew what the user's average download times were upon
their arrival, then this could be used to automatically determine what level
of information to display to the user before the first URL is actually
served.
I suggest that a client side header (for example "Avg Speed: 38552"
representing bits per second, say, could be useful. It is the responsibility
of the client to calculate and maintain this figure based on their average
or maximum download speeds over the duration of a browsing session.
The header should obviously remain optional in any client implementation,
but the benefit of supplying it is high.
tam
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
