Would it be possible / make sense to support storing css / js aggregates from this module in a cache bin, so I could store them in memcache? So, advagg provides a menu router entry at /advagg/%1, and when that is requested it returns the file out of the cache bin (in our case memcache).

I initially dismissed this as silly internally because it would require a Drupal bootstrap per-aggregate grabbed, but we're using a private file system, which does the same thing right now (and is really clunky in D6 in general).

Crazy / stupid idea?

Comments

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Status: Active » Closed (works as designed)

When using a private file system, AdvAgg gets around this by allowing one to change the root level from sites/default/files to something else that does not fall under the private file system. Your cache bin idea won't get us anywhere as the webserver (apache/nginx) is already serving the file. If its not, let me know!