On 12/06/2010, at 1:14 PM, Mike Bailey wrote:
One of the tricks to improving the performance of your website is to
optimize caching. By instructing browsers and proxies to cache assets
that don’t change very often (css, images, javascript), we can reduce
page load time as well as bandwidth costs.
By instructing browsers and proxies not to check for updated versions
of cached assets we can further speed things up. Google recommend the
use of fingerprinting to enable dynamic updating of cached content.
This simply means including a fingerprint of the resource in it’s URL
so the URL gets updated when the resource changes.
You know Rails has had this via asset timestamping for donkeys years?
My Rails 0.14.1 plugin from 2005:
http://aspn.activestate.com/ASPN/Mail/Message/ruby-rails/2870082
You just have to make sure to configure your HTTP server correctly.
Yesterday I added Fingerprint support to Paperclip. I've written it
up here:
http://mike.bailey.net.au/blog/?p=31
http://github.com/mbailey/paperclip/commit/885dc03c1e3e4fb7525ed7cab725bab4588be466#commitcomment-92949
-- tim
--
You received this message because you are subscribed to the Google Groups "Ruby or
Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en.
