I was tracking down an issue with the alldata.lzx test suite, and found that there is an issue with the "clientcacheable" flag on LzDataset. That flag controls adding the "__lzbc__" query arg with a unique value to each data request, to defeat the browser caching.
It's set to "true" by default, which seems wrong to me. It seems like in most cases, the user would like the browser not to try to cache data requests. I'd like to propose setting it to false by default. In most cases nobody notices the setting of this flag, because it seems like when you have a POST type request, the browsers don't cache it anyway. But for a SOLO GET request, if the browser doesn't add that unique value, the browser will return cached data. Now, I do remember someone asking at one time how to disable the cache-breaking query arg, and the way to do that is to set clientcacheable=true, but I really don't think this should be the default, it seems like it will lead to a lot of hard-to-find bugs for developers who don't realize that the browser may be caching SOLO GET requests. -- Henry Minsky Software Architect [email protected]
