ets-berkeley-edu/calcentral — pull request #318 by ctweney (2012-11-28 21:27:07+00:00)
Title: CLC-526 Invalidate caches in a reasonably decoupled way

JIRA: https://jira.media.berkeley.edu/jira/browse/CLC-526

This fixes the issue where the /api/my/status feed continues to show the old value of has_canvas_access after a Canvas token grant (or revocation).

This is the best way Ray and I could think of to make a relatively decoupled cache invalidator in our current stack. The UserCacheInvalidator class has knowledge of classes all over our code base, but it's the classes of concern themselves that do the actual Rails.cache.delete calls based on their own idea of what their cache key is.