expires_in is just a small use case of HTTP Cache mechanisms. The plugin supports :etag and :last_modified_at options besides :expires_in. In those cases, you can also send a Proc or an Array, allowing better and dynamic cache validation/expiration.
Second, if I want to cache several pages, it's better the declarative style on the top of my controller: http_cache :index, :show, :list, :common_options =>... And it's more DRY in comparison with setting expires_in in all actions. I hope that proves my point! =) Daniel. On 9 jun, 13:30, "Lisa Seelye" <[EMAIL PROTECTED]> wrote: > <quote who="Daniel Cursino"> > > > > > I finally decided to insert some HTTP Cache in my app (besides Rails > > default e-tag) and found one nice plugin: > > >http://josevalim.blogspot.com/2008/06/easy-http-cache.html > > > It gives me all tools to manipulate cache headers just declaring it in > > my Controller. > > Just curious but what's wrong with the "expires_in" > (ActionController::Base) Rails method? > > -- > Regards, > -Lisahttp://www.crudvision.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
