Presentation State Caching
Jon's Radio had a interesting piece today on UI of RIA (rich internet applications).
Going forward, we will move it one notch up to have a wrapping frame cache the modelRoot data and all content inside this frame will share modelRoot. This way modelRoot can be optionally retained across page refreshes. This is by the way the GMail approach.
For more views on this subject, see Jun's personal blog.
I entirely agree with the first point. Advanced widgetry alone will not save the day. We'll also need an intelligent cache -- along the lines of what the Alchemy project aimed to be.You know what? Cornerstone is already there in term of the cache. Our modelRoot is the presentation state cached in the client through which we can do wonderful things of DHTML.
Going forward, we will move it one notch up to have a wrapping frame cache the modelRoot data and all content inside this frame will share modelRoot. This way modelRoot can be optionally retained across page refreshes. This is by the way the GMail approach.
For more views on this subject, see Jun's personal blog.
<< Home