Ryan Tomayko

How to upgrade plugins to Rails 3.0 —

Using Rack::Cache as an example. Nice!

Slides from Stefan Tilkov's HTTP Caching talk @ JAOO —

Warning: PDF. This is probably the best high-level, everything about HTTP caching all in one place resource on the web at this point. Good stuff. I’m kicking myself for not being a part of his track at JAOO now.

Full Stack ETag Support —

This is how I am using Rack::Cache, Sinatra, and CouchDB … Sweet ascii diagram there. I’ve seen this ETag chaining technique twice just this week. The other one is gemcutter. They store gems in S3 and pass the S3 provided ETag along in their responses, so it’s like the web app is more of an intermediary sometimes. Weird and cool and interesting.

What to Look For in a HTTP Proxy/Cache —

mnot on how to evaluate different proxy cache options for your needs.

HTTP's Best-Kept Secret: Caching —

Here’s the slides from my RailsConf 2009 presentation on HTTP caching. I doubt the general info will make much sense without me talking over it but the diagrams should be fairly useful.

Scaling Rails - Episode #11 - Advanced HTTP Caching —

I haven’t actually had a chance to watch this yet but I’m sure it’s great if it builds on the talk Gregg gave at acts_as_conference 2009. Also, I love this slide: “Reverse Proxy Caches – WTF?” :)

Gregg Pollack presents Rack::Cache at acts_as_conference 2009 —

The RailsEnvy guys presented on a bunch of recent innovations in the Ruby/Rails community in their acts_as_conference 2009 talk. Go to 24:00 where Gregg gives a really tremendous overview of using Rack::Cache, the benefits of HTTP caching in general, and how to use all of this stuff in Rails 2.3.

How to setup and use Rack::Cache with Rails 2.3.0 RC 1 —

Huge thanks to christian for getting this up. I’ve been meaning to get something on the Rack::Cache site for some time now.

Easy client-caching with RestClient and Rack::Cache —

This is one the amazing benefits of having an insanely simple but well defined SPEC (Rack) around the edges of your library. It makes it trivial to hook things up in new and interesting ways.

Rack::Cache implementation annotations on RFC 2616 —

I’ve annotated RFC 2616 Section 13 with details on where Rack::Cache is and isn’t compliant. Anything not highlighted should work as described in the RFC. I think I’ll be using SharedCopy more in the future.

rack-esi —

Christoffer Sawicki has started in on a partial implementation of ESI (Edge Side Includes) as a Rack middleware component. Put something like this in front of Rack::Cache and things get real interesting real fast :)

Google Groups: rack-cache —

Mailing list for Rack::Cache users and hackers. Come on in, the water’s warm.

Introducing Rails Metal —

David Heinemeier Hansson: “Rails Edge adopted Rack a while back and we’ve been exploring ways to expose that better. The first thing we did was to make it really easy to hook up any piece of Rack middleware in front of a Rails request. In your config/environment.rb file, you can do: config.middlewares.use(Rack::Cache, :verbose => true)”

Oh hell yes.

A Collection of Rack middlewares —

It’s really starting to come together, isn’t it?

Ruby on Rack #2 - The Builder —

Pratik continues his series on Rack with a deep dive into Rack::Builder.

Smooth HTTP Caching With Rack::Cache —

Sebastien Auvray covers Rack::Cache at InfoQ. Thanks!

Rack cache headers —

Interesting approach to setting cache related headers using a Rack middleware component.

Rack::Cache is a good idea —

Ryan King nails it.

Advanced Squid Caching for Rails Applications —

So, I got an email yesterday disagreeing with my remark about HTTP caching being wildly under-appreciated in the Ruby web community. I felt bad, a little. Then I read this article (posted the day after my remark), which talks about Scribd moving to a Squid reverse proxy setup to front their Rails deployments:

“But there was a problem – no one uses caching proxies in 2008 :–) So, we’ve got an idea – why can’t we place such a server in front of our application and make it cache content for all users in the world?”

The fact that Scribd had to “have this idea” on their own and had not previously been exposed to a ton of literature/tools on reverse proxy / gateway caching is completely fucking unacceptable. I’m back to agreeing with myself.

What's New in Edge Rails: Even Better Conditional GET Support —

Much nicer, IMO. I’m interested to see if someone can get Rails + Rack::Cache working together so that you can maximize the benefits of generating these validators.