> This doesn't seem to work correctly - when I look at a > catalogue/moredetail.pl page for a bib that has more than one item, > the lost and damaged dropdowns for the first item are blank, but > populated for the second and subsequent items. That likely indicates > that the result is being cached but not returned the first time > through for a given authorized value.
Yes, I can see it, clear as crystal! I apologize for not being vigilant enough and thank you for being enough vigilant. I resubmit. > I think that we would be better off using the Memoize module or one of > its kin to implement this sort of caching. I will take a look. What Koha would need is a way to cache large dataset (biblio framework, authorized values, XSLT transformer, etc.) at application level not at script level. And if possible caching directly Perl object rather than serialized like with memcached (I really don't see how...) mod_perl is the solution but I fear that there is no incremental path for switching such a large code base as Koha into a mod_perl application. Otherwise, isn't it time to consider integrating OO framework like Moose, or something like Catalyst? and modernizing code. Sponsors with deep pocket required :-) Thanks. -- Frédéric DEMIANS http://www.tamil.fr/u/fdemians.html _______________________________________________ Koha-patches mailing list [email protected] http://lists.koha.org/mailman/listinfo/koha-patches
