Thanks Mark.
I find the stale data concept interesting. I'm going to challenge you on that one :).
Is it because you are just testing, and beating it up, wheras in real-life use it wouldn't be perceived as stale?
Contact info - this can be stale as you switch between tabs. If you go to contact info then to activities, then back to contact info...sure....it can be stale. But only while you are on *that* specific email. If you click on another email and then back to that email, it is a fresh pull. So how long are you really spending on that contact info tab while reading the same email, where that contact info could really become stale and out of date?
Search - each time you click the search it is a fresh pull. So that isn't stale.
Activities, Transactions, Cases, Opportunities and Documents - these do a fresh pull each time you click in the tab. So that doesn't stay stale.
Add Activity / Case / Opportunity - these are loaded once, and then if you click to a different tab and back again, the data is cached and stale. But only for that one email at that one instance. As soon as you click on another email, it is a fresh pull. Real life use case where that's a problem?
Settings - always a fresh pull.
As you can tell, we've paid a lot of attention to keeping things out that really aren't needed, so that what we have left is elegant, simple and fast.
So, I really need to see the real life use case of stale data before I start adding clutter with reload buttons!
Thoughts?
Paul
P.S. We going for pints at Scaling New Heights?