[Koha-devel] [Discussion Tech] Cache handling in koha

MJ Ray mjr at phonecoop.coop
Thu Feb 9 11:18:51 CET 2012


Tomas Cohen Arazi <tomascohen at gmail.com>
> Back to the ENV use I think we must make a desicion:
>  - Do we want to cache koha-conf.xml ?

Yes, I think so.

We were burning time on every request reloading it, weren't we?

[...]
> 2) Memoization in Koha
> Do we plan to use memoization in the mid/long-term? Or are we thinking
> of a more abstract set of 'cache' utilities which provide an interface
> to memcached?
> 
> Using memoization is nice, clean and simple. It has the disadvantage
> that caching is done in an implicit way, and there are hidden problems
> (read side-effects) that have to be taken into account. For example,

Is there a good list of the example disadvantages somewhere?

Have other projects made this decision faced with similar circumstances,
and can we see their reasoning?

Hope that helps,
-- 
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op.
http://koha-community.org supporter, web and library systems developer.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire (including development) at http://www.software.coop/


More information about the Koha-devel mailing list