Page caching is an easy way to get massive performance and scalability increases with little up front effort.
Of course, when page caching, a number of design changes are necessary. For example, server side session data cannot be used to render data on cached pages.
Rails provides the flash hash to easily render alert messages and errors. In the controller you can write to the flash hash:
flash[:error] = "You cannot go there"
flash[:notice] = "Welcome to eternity"
and render the flash hash in the view. Typically the rendering happens on a layout:
<div id="error_div_id" class="flash flash_error"><%= flash[:error] %></div>
<div id="notice_div_id" class="flash flash_notice"><%= flash[:notice] %></div>
There are some strange quirks with using flash such as needing to use FlashHash#now when rendering the response without redirecting.
Everything works great until you need to page cache the landing page.
For example, lets say you page cache your home page. After logging in, you are redirected to the home page with the flash notice “Logged in successfully”. When page caching, this solution does not work because the request is responded to by the Web Server (i.e. Apache) and does not reach the Rails App server (i.e. Mongrel).
This means the view does not get a chance to render the flash error and notice.
There are a couple of solutions to this problem.
- Do an AJAX request back to the server to render the flash error and notice (i.e. using RJS)
- Send the flash error and notice from the server with cookies and render it during page load
Introducing Cacheable Flash
To solve the problem using cookies on Peer to Patent, we wrote the Cacheable Flash plugin. The plugin allows you to set the flash hash as normal on the controller. It handles converting the flash hash into cookies. All you need to do is include the CacheableFlash module into your controller.
class ApplicationController < ActionController::Base
<div id="error_div_id" class="flash flash_error"></div>
<div id="notice_div_id" class="flash flash_notice"></div>
The Flash.transferFromCookies method:
- Grabs the flash data from the cookies and saves it to Flash.data
- Erases the flash data from the cookies
The Flash.writeDataTo method:
- Writes data from the passed in key in Flash.data to the passed in element or element id
Here is how the life cycle of the login works:
- The user enters the correct login information
Rails handles the web request. In the Login controller, flash[:notice] is written to
flash[:notice] = "Welcome to Eternity"
An after filter serializes contents of the Flash Hash as JSON into cookies
- The after filter clears the flash hash
- The cached page is rendered
- The client side receives and clears the flash cookie data
There is also a side benefit — you don’t have to use FlashHash#now because storing the flash in cookies to be rendered and erased by the client makes this unnecessary.
The Cacheable Flash plugin is on the Pivotal RB project page (http://rubyforge.org/projects/pivotalrb). You can install it by running:
ruby script/plugin install svn://rubyforge.org/var/svn/pivotalrb/cacheable_flash/trunk
It will copy flash.js, cookie.js, and json.js if you do not already have these files.
Happy Page Caching!!
Thanks to Josh Susser for pairing with me on this.