>>>>> "PG" == Peter Guzis <[EMAIL PROTECTED]> writes:
PG> <bad morning> PG> Thanks for the positive feedback. Glad I could help. You've obviously never had to support end-users' browsers. Ideally every server would send the correct headers and we would all live in the happy town of CacheLand. The reality is: different browsers interpret different headers differently and the headers themselves are almost as much of a crapshoot as trying to write cross-browser JavaScript. Many sites don't even send the right headers or omit them outright. Let's not forget overzealous caching proxies too. PG> </bad morning> Could you wrap your lines? Thanks. Yes, I do support a rather large community using our service, and everything works just as expected because our server sets expiry/nocache on select pages properly. Seriously, if you're building an app that expects pages to be fetched every time, then your server should say so when it delivers the pages. The only times this fails is when the client's clock is off by something like a few months or more, which causes many other issues, let alone bad cached pages, or they're using an older Opera with its insane defaults to ignore the nocache settings (but almost nobody uses it so it is pretty much a non-issue). _______________________________________________ templates mailing list [EMAIL PROTECTED] http://lists.template-toolkit.org/mailman/listinfo/templates
