The problem with whole page caching is that for a given URL, all the content must be the same. For dynamic websites, this is a poor solution. People are used to seeing Hello, Bob and extra menu items if the user has access to more features.
Instead of full page caching, you could do partial page caching but that means more server work and more disk reads. In the previous blog entry, Veneer has a nice full page caching feature so Veneer will work around the problem.
Using a nice javascript cookie library from Paul Stephens, Veneer can parse the fields the cookie fields and adjust the Dom accordingly.
There is another problem. The URLs change depending on which module is being used. Routing in Veneer is /module/action or /controller/module/action. How does the javascript parse the URL? A quick google search produces a url parsing library by Steven Levithan.
Now, if the user is logged in, the name is stored on the client for personalization. The member level is stored on the client so if the client is an admin, a context sensitive admin link is placed in the admin area.
Sunday, November 4, 2007
Subscribe to:
Posts (Atom)