Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
For #220 use -M comparison as more efficient.
- Loading branch information
Showing
3 changed files
with
18 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7d658dd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NB Just some ponderings - not criticism of the above - you were too quick with a commit! :)
It feels like there might be something different to be done with
EPrints::Update::Static::update_auto
off the back of this (which is part of the EPrints::Apache::Rewrite handling of requests for auto-x files)?Could/should the timestamps be cached in
$repo->{auto_js_timestamp}
(or similar) - like the caching of phrase file timestamps?With the above, I think that generating a static page will check the file times, and serving a request for the auto- file will also check the file times.
One or other of these is probably unnecessary? (I think checking it at the request side of things is best - and then caching it into
$repo->{auto_css_timestamp}
).If you're running a
generate_abstracts
, does the complete template (including timestamped css links) get cached once, and re-used, or would the above checks be conducted for every abstract generated?Should we also look at including integrity checks for these files?