"tshad" wrote:
I'll go ahead and try that. That sounds like that will solve my problem.
I can't run the site assuming the user will have his browser set up a
certain way and I would have no way to know if his bowser is caching the
pages (although I suspect there probably is a way to check this). I don't
want him getting errors because of his caching.
Hi, keep in mind that while there are techniques which can be used to try to
handle caching, they cannot be guaranteed to work for all users either, based
on their settings and browsers. The solution using the directive will
probably work for most of your users, however, and is probably "good enough".
Also keep in mind that this will degrade the performance of your pages
which use this technique. If your pages are not dynamic and only change once
in a while (new content every few days, etc), then it may not be worth
slowing down the experience for all users, just to make happy the few people
who use this non-standard browser setting.
You have to bite the bullet and make certain assumptions about how a browser
is setup. If you still deny this, are you going build your site to also
support users who have disabled javascript and cookies in their browser?
There are probably many more of those than who have set their browser cache
to never check for new pages. While its certainly possible to design your
site to handle these types of users, you need to ask yourself if its worth
it, or if you maybe should have clearly defined the baseline requirements
during early development. Otherwise you are headed down a very slippery
slope of spending all your time supporting a tiny percentage of users, at the
expense of most of your users.
