Rails%203%20In%20Action

2. Very quick check for
/public/projects/1.html
3. Not found...
Go to the application!
4. Application routes
request to controller
Page and action caching
In development mode, caching is turned off by default. Obviously, in development
mode you don’t care so much about caching, as all requests are going to be local and
not on a heavy-load server. You can turn caching on by going into config/environments/
development.rb and changing this line
config.action_controller.perform_caching = false
to this:
1. Request comes in for
GET /projects/1
Browser
Web Server
/public/projects/1.html
Application
config.action_controller.perform_caching = true
Without this option, you can still have caches_page in your controllers, it just won’t
do anything. With it turned on, your pages will be cached upon their first request.
Launch rails server again and this time go to http://localhost:3000/projects/1.
In the server output, you’ll see an additional line:
Write page /.../ticketee/public/projects/1.html (0.3ms)
2. Very quick check for
/public/projects/1.html
1. Request comes in for
GET/projects/1
Controller
Browser
Web Server
/public/projects/1.html
6. Request sent back to browser
5. Controller creates
/public/projects/1.html
4. Page sent back to browser
449
Figure 16.4 First request, no cached page
3. Found! It's dangerous
to go alone, take this
Figure 16.5 Subsequent
requests, cached page