rubyonrailsin

On Mar 24, 9:51 am, Jim Gay <j...@saturnflyer.com> wrote:
> There is an issue for per-key purging http://github.com/radiant/radiant/issues#issue/82 which would require
> something likehttp://github.com/svenfuchs/rack-cache-purge(unless it
> gets pulled into rack-cache proper).
> But even with that, there still would need to be an index of what
> content includes what other content if you wanted page saving to only
> expire a single cache key.

Andrea Franz's DynamicPage extension is intended to provide that
context.

You use it by marking a page as "Dynamic" and when a new page is
created, the extension walks up
the list of ancestors, and for each ancestor marked "Dynamic" it would
remove that page from the
cache.

I think the functionality described in http://github.com/radiant/radiant/issues#issue/82
fits this
scenario perfectly.

So is this http://gist.github.com/275240 the best way invalidate the
cache programmatically?

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/

To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.