Re: last update

Robert Hazeltine (rhazltin@zeppo.nepean.uws.edu.au)
Tue, 9 Jan 1996 09:42:22 +1000 (EET)


Date: Tue, 9 Jan 1996 09:42:22 +1000 (EET)
From: Robert Hazeltine <rhazltin@zeppo.nepean.uws.edu.au>
To: Abigail <abigail@tungsten.gn.iaf.nl>
Cc: www-html@w3.org
Subject: Re: last update
In-Reply-To: <199601082159.WAA23789@tungsten.gn.iaf.nl>
Message-Id: <Pine.A32.3.91.960109092859.28588A-100000@zeppo.nepean.uws.edu.au>

Abigail,

On Mon, 8 Jan 1996, Abigail wrote:

> It's not a 9-10 characters, it's the fact your whole document has to
> be send again. Suppose your document is 50k, then the following is
> not unlikely:
> 
> Reader visits your page, downloads 50k data, storing in her cache.
> >From the page, she goes to the next page, and the next.
> After a few pages, she selects 'top' (pointing to your first page).
> Her browser sends a 'get-if-modified' request. The server knows the
> requested document has an SSI, so the requested document has to be
> genereted *now* and is hence "modified", sending 50k again....
> However, she has identical information in her cache.

Thanks for repeating this simple fact of life on the Internet.  It 
obviously bears repeating ad nauseam.  A little bit of considerate 
drafting of HTML avoids problems for lots of people, all of whom do not 
have the last and greatest of hardware or bandwidth.

Unfortunately, there is a proliferation of counters and the like which 
have exactly the same adverse effect on bandwidth.

Rob...

Robert Hazeltine                    r.hazeltine@nepean.uws.edu.au
Library Web Support                 http://www.nepean.uws.edu.au/library/
                  University of Western Sydney, Nepean