similar to: Does Bdrd 2.x handle fragment caching still?

I''m just getting my hands dirty with caching. The pages I want to cache have some user specific data on them (for example "log out"). That sent me down the route of fragment caching. One of the things I want to pagination is a paginated list. My question is how is pagination and query strings handled with fragment caching? Does each page get its own fragment and query string

I''ve written a plugin to allow for time based fragment caching. It lets you do things like: <% cache ''fragment_name'', 10.minutes.from_now do %> <p>something intensive which will be cached for 10 minutes</p> <% end %> Also, there''s a convenience method so that in your controllers you can do: when_fragment_expired

Hi All, I''d like to use different caching strategies based on the visitor status - anonymous => action caching - logged in => fragment caching Is that doable? Where should I start? TIA Alain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

Hi, In my view I have the following cache: <%- cache(:controller => ''products'', :action => ''index'', :action_suffix => ''footer'') do -%> ... <%- end -%> And that''s the file generated: tmp/cache/views/www.mysite.com/products.action_suffix=footer.cache Why isn''t fragment caching picking up the :index

I''m trying to setup some fragment caching which works fine for the index but i''m not sure how to ignore the caching if they are searching the index results. my code in short: ItemsController def index @items = Item.search(params[:search], params[:min_rank], params[:max_rank], params[:classification_id], ...) end index.html.erb <% cache (''items'',

Hello, I''m having problems on both my production and development servers with fragment caching. Every time I try to cache something using <% cache do %>, I get the following error: Couldn''t create cache directory: views/0.0.0.0:3000/jobs/106/questions/ 174 (wrong number of arguments (2 for 1)) but strangely, all of the directories apart from the last one are created.

Hello. I wouldn''t mind getting some feedback about the use of fragment caching. I''ve got a series of relatively expensive database queries with their respective partials cached and everything is working fine. The problem is that do get this to work I''ve had to move the database queries from the controller into the view layer so as to avoid them being called if the

Hi, I am trying to do fragment caching using :mem_cache_store. However, when I compare it to fragment caching using :file_store, it seems to be a lot slower. Here are the results: uncache Completed in 2.20246 (0 reqs/sec) | Rendering: 2.19891 (99%) | DB: 0.00017(0%) | 200 OK [ http://127.0.0.1/] using file_store Completed in 0.00952 (105 reqs/sec) | Rendering: 0.00702 (73%) | DB: 0.00000(0%)

Hi, with fragment caching one can cache parts of a page. However, more often than not what I would need is the exact opposite approach. I would like to be able to use action cashing and have a mechanism for telling Rails to exclude one or more areas from the cashing and fill them with dynamic content instead. A good example would be a page where all content would be perfectly cachable but one

Doing some reading up on fragment cache before implmenting it and had a few questions: 1.) I read that page and action caching have issues or don''t work at all with query strings (more so with page caching). Does fragment caching work with query strings? i.e something like example.com/foo/bar?page=2 2.) If the above is true and I have an authentication system built into my app, if 2

I can''t seem to get the fragment cache to use :file_store. I''d really appreciate it if someone could point me in the right direction. Rails 1.1 final, FreeBSD Observe: In environment.rb AND production.rb (for good measure, DRY be damned): ActionController::Base.fragment_cache_store = :file_store, "/www/apps/localfeeds/directory/tmp/fragmentcache/" At the console

Hi All, We have four domains setup for The Couch: thecouch.org.nz, thecouch.co.nz, www.thecouch.org.nz and www.thecouch.co.nz. They are all handled by the same rails app. The means that fragment caching creates four folders in our cache directory, named after each URL. This introduces two problems: 1: We are caching 4 times as much stuff as necessary 2: Our cache sweepers are only sweeping one

Hi All, We have four domains setup for The Couch: thecouch.org.nz, thecouch.co.nz, www.thecouch.org.nz and www.thecouch.co.nz. They are all handled by the same rails app. The means that fragment caching creates four folders in our cache directory, named after each URL. This introduces two problems: 1: We are caching 4 times as much stuff as necessary 2: Our cache sweepers are only sweeping one

Hello, I''m trying to figure out how I could implement fragment caching that expires every x amount of time. I thought of writing a runner script that would expire the cache and set it as a cron job, but that doesn''t really work because runner scripts act on models and not controllers. Does anybody have any ideas? Regards, -carl

Do you have any hint for using fragment caching within a RJS response? I''ve the following piece of code in a rjs template for hotel in @hotels cache(:id => hotel.id, :format => params[:format]) do page.insert_html(:bottom, :items, :partial => hotel, :locals => { :city => @city, :country => @country }) end end but when the response is rendered it returns the

I have a controller which iterates through a group of people and dynamically generates an email for each person, it is a bit DB heavy so caching would really help. Adding ''include ActionController::Caching::Fragments'' to my BookingMailer model produces this error: ActionView::TemplateError (undefined local variable or method `perform_caching'' for

<% cache(:part => @user.id) do%> in the file controller => users, action => show. Regardless if you put the action so it ends up as <% cache(:action => ''show'', :part => @user.id) do%> or the controller, the file will come out in "tmp>cache>`SERVER`>users>show>1.part=userid#.cache . Which is fine except for the 1 in the cache

Hi all, I am trying to use backgroundrb to cache a set of controller actions that are quite processor expensive (there is some pretty heavy xml processing going on). In my rails app I have page caching set up to observe the appropriate controllers and models and all works well. However when model changes occur in a backgroundrb process the cache sweeper isn''t notified of the changes

I''m at a loss to explain a very strange error I''m getting. This seems to happen on our production system where we have a backgroundrb server sharing a host with a Rails app running on Mongrel. The first one or two, occasionally three, calls to a worker (direct MiddleMan calls from Rails, not scheduled) succeed, but afterwards, the server fails to initialize new workers.

I have a page that requires a lot of DB access to create a section of it, but that section does not change very often. I know how to cache the fragment in the view, but the db is still accessed in the controller. I watched the railscasts on fragment caching and he does it by moving the logic to the model. Is that the only way to do it? The part of the page that changes on every display is the