http://localhost/ticket/541 <p> The simplest way to improve performance on specific pages is to implement full page caching. </p> <p> This, however, has challenges on pages with user-specific content. For example, on CKAN when a user is logged at the top of the page we have "You are logged in as: {username}". Similarly we change the visibility of some material depending on the status of users: </p> <ul><li>Visibility of Edit or Authz link on packages and groups </li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/541 Trac 0.12.3 dread Thu, 13 Jan 2011 11:12:35 GMT http://localhost/ticket/541#comment:1 http://localhost/ticket/541#comment:1 <ul> <li><strong>priority</strong> set to <em>awaiting triage</em> </li> <li><strong>type</strong> changed from <em>story</em> to <em>enhancement</em> </li> <li><strong>component</strong> set to <em>ckan</em> </li> </ul> Ticket wwaites Thu, 13 Jan 2011 13:21:12 GMT http://localhost/ticket/541#comment:2 http://localhost/ticket/541#comment:2 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> this is implemented with the cookie javascript technique. not so suitable for pages where content is radically differerent depending on the logged in user but for small bits like the logged in status works perfectly well, likewise for edit links. </p> Ticket