Sign in through GitHub
Applied Filters: Caching x
Page Caching (revised)
Episode #89Feb 02, 20124 comments

Page Caching (revised)

Page caching is an efficient way to cache full content to be served by the front-end web server. Learn how to deal with pagination, expiration with sweepers, and user-specific content in this episode. (9 minutes)
HTTP Caching
Episode #321Jan 30, 201222 comments

HTTP Caching

With HTTP response headers you can the cache in the user's browser and proxies. Etags, Last-Modified, Cache-Control and Rack::Cache are all covered here (15 minutes)
Touch and Cache
Episode #172Jul 27, 200914 comments

Touch and Cache

Rails 2.3.3 brings us a new feature called "touch". See how to use this to auto-expire associated caches in this episode. (6 minutes)
Dynamic Page Caching
Episode #169Jul 06, 200949 comments

Dynamic Page Caching

Use JavaScript to allow dynamic content in a page cache. In this episode I show you how to insert the user-specific content into a page through JavaScript. (11 minutes)
Caching in Rails 2.1
Episode #115Jun 23, 200847 comments

Caching in Rails 2.1

Rails 2.1 brings some new caching features which makes it very easy to cache any values including models. See how in this episode. (8 minutes)
Action Caching
Episode #93Feb 17, 200818 comments

Action Caching

Action caching behaves much like page caching except it processes the controller filters. You can also make it conditional as seen in this episode. (7 minutes)
Fragment Caching
Episode #90Jan 27, 200823 comments

Fragment Caching

Sometimes you only want to cache a section of a page instead of the entire page. Fragment caching is the answer as shown in this episode. (6 minutes)
Page Caching
Episode #89Jan 20, 200819 comments

Page Caching

Page caching is an efficient way to cache stateless content. In this episode I will show you how to cache the dynamic javascript we created last week. (6 minutes)
Caching with Instance Variables
Episode #1Mar 04, 200727 comments

Caching with Instance Variables

Learn a quick way to improve performance. Just store the end result of an expensive command in an instance variable! (2 minutes)