[Zope] No-cache

[Joe Goldthwaite]

Don't worry, I'm being careful.  The program works perfectly with IE.  It
works with Firefox but you have to hit the refresh button if you want the
options from the lower pages to display after you've moved back.  That will
do until I figure out how to get Firefox to work correctly.  It may be a bug
in Firefox so the problem might go away by itself.

-----Original Message-----
From: kosh [mailto:kosh at aesaeion.com]
Sent: Thursday, July 29, 2004 10:53 PM
To: joe at goldthwaites.com
Subject: Re: [Zope] No-cache


On Thursday 29 July 2004 11:03 am, Joe Goldthwaite wrote:
> Sigh...  I know what you mean.  We're virtually an all IE shop.  I think
> I'm the only one using anything besides IE.  My old method passed all the
> options in the URL.  That meant that if they were looking at a specific
> organization and moved around through the fiscal periods, and other
> reporting options, they had to move back through all those same options to
> get back to the parent page.  Avoiding that is worth working around the
> browser quirks.  Still, there are times when I miss my old green screen
> programming environment.
>

Be very careful with stuff being IE only. You lock yourself into specific
quirks of specific browsers. Also Windows XP SP2 looks like it is going to
break a lot of IE specific stuff with its various security fixes. I know at
least some places that are put into a situation of having security issues
fixed or having their apps work and since they are so IE specific they are
looking at having to rewrite them mostly from scratch to make them work.

I have also found that since there is NO IE standard and never has been and
likely never will be the quirks are very much quirks. They tend to break at
any time for almost no reason. I have seen things like updating office
breaking IE specific apps. At least if your app is cross browser if it
breaks
in one of them you can use the other one until it is fixed. So business can
continue with almost no interruptions. If your app is IE only then it is not
a web application it is a windows application and you would have been better
off just making it a regular windows app and no using a webserver at all
since it is just introducing another source of problems.