rubyonrailsin

On Wed, Mar 24, 2010 at 12:41 PM, Mislav Marohnić
<mislav.marohnic@gmail.com> wrote:
> On Wed, Mar 24, 2010 at 17:34, Jim Gay <jim@saturnflyer.com> wrote:
>>
>> Radiant::Cache.clear
>
> That deletes all cached files. I wouldn't use this aggressively—Radiant
> already uses it too much (on every create/update/destroy action) and I
> wanted to make this better so it will never be called again unless there is
> real need to delete absolutely all cached data.
>

Well, Radiant is aggressive about it because there is no easy way of
knowing what page, snippet or layout contains what parts of other
pages or snippets. There's no registry of content to know where some
cached page should expire and some other cached page shouldn't.

There is an issue for per-key purging
http://github.com/radiant/radiant/issues#issue/82 which would require
something like http://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.

--
Jim Gay
http://www.saturnflyer.com

--
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.