Hey Matthew, > Sorry for my late response. Our internet no worky.
No worries! Interesting to hear that there was an extraction of "heroku_rack", but it's since been taken down. > It seems to me likely that Heroku may have something like (but perhaps more > sophisticated than) "use Rack::StaticCache, :urls => ['/favicon.ico', > '/images', '/javascripts', '/stylesheets'], :root => 'public'" early in the > Rack stack, directing any traffic away from my own StaticCache attempts. Yes, either that, or they simply modify headers on the way out of the rack stack. > > Let's hope the Heroku team will enlighten us as to exactly what happens in > > their stack when they see a call to Rack::File. > > I hope so, too. While I can appreciate the benefits of "implementation > hiding," it sure would be helpful to see the code. If any of the Heroku team are listening, I don't necessarily need to see your code, just would appreciate clarification on what you're doing with calls to Rack::File (I'm assuming that's what's being intercepted and handled in a specific way). > > (though rather than overwriting ActionView::Helpers::AssetTagHelper, I've > > just written my own js_tag and css_tag helpers). > > Chicken. :-) Indeed! Seriously though, it was actually because I wanted something framework agnostic. > > But I think I would prefer sacrificing busting the cache on each deploy > > rather than having Ruby read the contents of my JS and CSS files (which can > > be quite large) on *every* request. > > That's a good trade-off to note. (In my current context, there are 3 small > assets, and AssetTagHelper caches the digests -- so they'll just be > recalculated once per dyno.) Where does AssetTagHelper cache the digest? How does this persist across multiple requests? Isn't the digest being generated on each request? Thanks for sharing your thoughts. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
