Hi, I''m experimenting with a DB design that is very flexible, but makes it very slow to display data (I really want to push that DB design to its limits to see if it is applicable, I don''t plan to change it for my experiments). That''s why I want to use Ruby on Rails'' caching. Let''s say we''re looking at a contacts database, and I display the list of the contacts I have in the database. I can specify an sort order, and I use the paginator to limit the number of contacts displayed on one page. The system is multi user and each user has his own contacts. I would like to cache as much as possible, but need to expire the cache as soon as it is needed. For each sort order, I would cache the resulting list. Each sort order has multiple (paginator) pages of contacts, and I also would like to cache each page that has been accessed. However, when the user enters a new contact, all his cached pages need to be expired. I would like to not expire other users'' caches if it is not necessary. I began to think about how to organise the caches pages, and though about this user_id > contacts_list > sort_order > page_number If I also have customers on the database, I would have user_id > customers_list > sort_order > page_number As some authentication and permission checks should happen, I thought to use action caching, but action caching doesn''t take into account all parameters passed in the URL. (it works with controller.url_for) Is what I want to do possible? Does anyone have advices on how I could use the RoR caching facilities? Is action caching with taking @params into accounts a good idea? Thanks. Raph