All of our Skuid pages are housed within full-screen Visualforce pages. We’ve been experimenting with cache=“true” and expires=x (where x is the time until the page expires) in the Visualforce pages so as to cache repetitive information, like the nav bar, logo, page structure, etc. Some of our Skuid pages are quite meaty, so this can have a dramatically positive effect, for example reducing the load time for one commonly used page from 5sec to 1sec for every repeat load. But it’s raised some questions:

1. We have a client page with a tabset, and one of the tabs is for Services, which displays a table. I have the VF cache expiry set to 10mins. If I edit one of the services, navigate to another page, then return to the client page (which is clearly being served from cache) and that same service, it displays the old value. If I hard refresh the page (shift-refresh), I get the fresh client page and the new service value. This seems odd, because the Service tab is set to lazy load, and in fact we use a little Javascript to run updateData when the tab shows (to speed up initial load even further). Given that the service data has changed, I’d have thought we’d get the new service value despite the client page being served from cache. Any thoughts?


2. If we set the expiry time to a high value (say several hours), we’ve run into issues where the popup message to login again appears. Can’t quite understand this. Our session timeout in Salesforce is set to 12 hours and the expiry was set to 8 hours in one test and we were repeatedly seeing the popup. I can test more thoroughly, but I wondered initially on what basis that popup appears.