josevalim/active_model_serializers — Issue #45: Add coarse support for caching/cache expirey
Author: elight
Created: 2012-03-05 18:14:31+00:00
State: open

Talked to Yehuda about this at Ruby on Ales last week.

We believe that it should be possible to provide a default caching/cache-expiry mechanism via AMS. Ideally, it would be able to support action caching for actions not requiring authentication and fragment caching (still really caching the whole action) keyed in part by user ID for authenticated users.

I've already started tinkering with this. Ultimately, I intend to submit the capability as a pull request.

I have a proof-of-concept that already has working cache writes via AMS -- though it's not on github just yet as I'm still recovering from RoA ;-). Plus I intend to write up a full failing test case for it to demonstrate the API that I'm suggesting. I hope to have something interesting to show in the next few days.