https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22473 Bug ID: 22473 Summary: Use koha-conf.xml modification time as cache key Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs@lists.koha-community.org Reporter: robin@kallisti.net.nz QA Contact: testopia@bugs.koha-community.org Target Milestone: ---
From this IRC conversation:
<fridolin> rkrimme1: did you flush memcached ? <magnuse> can't hurt :-) <magnuse> and yeah, i think you have to, for changes to koha-conf.xml to be picked up if this is the case, when creating and accessing memcached for koha-conf values, the actual modification time of the koha-conf should be appended to the key values. This means that if the file is updated, the cache is automatically invalid. It requires running stat on each request, but as the koha-conf file isn't actually being opened and parsed, this will be very fast. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.