Skip to content

Auto cache busting based on source files #143

Closed
wants to merge 2 commits into from

4 participants

@gwkunze
gwkunze commented Oct 20, 2011

See #116

Attempt to add cachebusting based on file modification times or file contents.

Works in my limited use-case. Not sure if it will work in every case. Still needs unit tests.

@kriswallsmith
Owner

What is the advantage of providing these different strategies? Why not just provide one?

@gwkunze
gwkunze commented Nov 2, 2011

I added the last-modified-time mostly because it was easy to add and because a similar feature is available in the WebAssets library (which I also used as inspiration for the options name).

The last modified time is faster and should generally work adequately, especially during development. However in our deployment scenario (multiple machines and hosted from S3) the modified time of different machines will be different due to the deployment process not starting at the exact same time. This would result in separate filenames in S3 for each machine which in term would lead to clients having to cache multiple versions if the loadbalancer directs them to a different machine.

@schmittjoh
Collaborator

alternative implementation for #190

@fran6co fran6co referenced this pull request Sep 4, 2012
Merged

adds CacheBustingWorker #297

@stof
Collaborator
stof commented Sep 13, 2012

Closing in favor of #297

@stof stof closed this Sep 13, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.