Richard Schneeman wrote: > The confusing part was > that the sweeper gets called no mater what, but the expire_fragment only > works on the specified actions.
I actually gave up on the sweepers in my app, as they were far too general, and expired more than was necessary in some cases, and given the filters and sorting that can be done, it's all fragment caching. Now the models decide which of their own fragments to expire (via Rails.cache.delete) depending on what was changed. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
