hoodwink.d enhanced


Railstorm #

by why in cult

It’s all over the place, yeah. And, yet, all together. You’ve got Technoblog. You’ve got railz0r3d!! And jlaine, which has this great article I missed on caching with Rails and up.

Using action caching means that the request will go through Action Pack so all the filters are processed before the page gets served. That way you can use authentication and other magic in your pages without having to give up the glory of caching.

The most granular way to do caching in Rails is fragment caching. It’s what the two higher-level caching schemes use internally. Using fragment caching is a gem when you have pages that have both highly dynamic and pretty static parts. The downside is that it’s a bit more work and you have to do it in templates.

I mean what better way to get into this stuff than sliding just enough code within your vision. (via del.icio.us.)

said on 03 Feb 2005 at 08:21

The last three projects to be registered on RubyForge have all been RubyOnRails-related… good times!

Comments are closed for this entry.