true enough!
a shift+refresh is also a good way to go (forces a refresh from the server).
This is/was particularly bad with AOL users as AOL was passing cached copies
of pages to the browser from their own server, not the server the site was
actually on.
I was pulling my hair out with the effects of this a few years back when I
made a menu (food menu) for a client that changed daily. Many of her
friends were swearing there was no change, when we knew for a fact that
there was. the common denominator was the users were all AOL subscribers.
the solution was to add _cgi between the file name and the file extension
like menu.htm became menu_cgi.htm... that and a note to shift+refresh...
Welcome to the internet. LOL
--
Have you seen ContentSeed (
www.contentseed.com)?
--
Chris Leeds
Contact:
http://chrisleeds.com/contact
NOTE:
This message was posted from an unmonitored email account.
This is an unfortunate necessity due to high volumes of spam sent to email
addresses in public newsgroups.
Sorry for any inconvenience.