> The best way to clear the cache is > <% Response.CacheControl = "no-cache" %> > <% Response.AddHeader "Pragma", "no-cache" %> > <% Response.Expires = -1 %>
That's good for the login page. It's not a good idea to have those settings for everything though. We have a very aggressive caching policy with expiry set to 1 year so the browser hardly ever has to even enquire of the server if a file is out of date. We also have a layer on top of the comms which groups together AJAX requests. I recently had to login to our qooxdoo app from Australia using a dial-up modem and got quite acceptable performance (I had previously logged in from the UK with broadband). If you turn off all caching then every request for common items like an image will generate another request to the server. We got particularly bad performance with third-party editors. We can turn on aggressive caching because we can setup the base URL with our version number, and force the browser to get everything fresh if we want it to load new scripts or images into its local cache. The only problem is testing during development. I use Firefox for most day to day testing and it's a very simple keysequence to clear the browser cache: ctrl+shift+delete, enter. Hugh ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
