Menu:

New in PyLucid: Page cache cleanup...

tag cloud blog | browser | ColorMirror | creole | database | development | django | django-weave | documentation | fastcgi | IRC | javascript | plugin | pylucid | release | security | standalone | test | web

↑ New in PyLucid: Page cache cleanup...  #

Before 7 months, 4 weeks published by jens.

With changeset:2469 the page cache would be cleaned after a model has been edited or created. (e.g. after PageTree, PageMeta or PageContent changed.)

This fixed http://trac.pylucid.net/ticket/317 and http://trac.pylucid.net/ticket/335

The Problem in ticket 335: Cleaning the cache is not only necessary so that the client sees the updates also. If a page is no longer accessable for anonymous, they should no longer be delivered from the cache.

We clean the complete page cache for one site, because we can't known witch part of the cache has been really changed. e.g. the update journal is somewhere or if the PageTree hierarchy change...

You will get some information about the cleaning if settings.DEBUG is on or you are a superuser.

You must update your environment, read: update existing PyLucid environment

(Last update: Dec. 3, 2009, 8:41 a.m. by jens.)

tags pylucid
0 comments:
    there exist no comment
Leave a comment

tag navi developing
Fork me on GitHub