Most of the resources on our site are fairly static, but not static enough to use the perpetual UFI method. They are not tied to version-control so deployment_id isn't perfect either, and mtime/md5 needs to constantly poll the filesystem. So we are currently testing with another UFI method that creates a new identifier each time the drupal caches are flushed.

Still need to figure out if it is better in the long run for our specific use case, but in any case it has come in handy when debugging so I though I'd share...

CommentFileSizeAuthor
cache-ufi-method.patch588 bytesmr.baileys

Comments

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

While it makes sense for testing, you are aware that this means the URLs of files that haven't changed will also change? I.e. files that have already been downloaded will be redownloaded by the user.

mr.baileys’s picture

mr.baileys
Primary language Dutch
Location 🇧🇪 (Ghent)
commented

Yup, we are using it on a subset of files, and use it to aid in validating our cache stack (so more of a testing tool as you say). On the live site most files will be running mtime.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Needs review » Reviewed & tested by the community

Makes sense. I'm going to rename it from "cache" to "Drupal cache" though, and mention that the cache is flushed e.g. when you submit the /admin/modules form.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Title: Provide an UFI method based on Drupal cache flush. » Provide an UFI method based on Drupal cache flush
Assigned: Unassigned » wim leers
Status: Reviewed & tested by the community » Fixed

D7: http://drupalcode.org/project/cdn.git/commit/71011e0
D6: http://drupalcode.org/project/cdn.git/commit/b241ecd

Improved description and added documentation, renamed from "Cache" to "Drupal cache".

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.