RFCs for Koha 3.4
RFCs for Koha 3.4
This page contains RFCs for version 3.4 of Koha. All RFCs for major new features for Koha 3.4 should be posted to koha-devel and copied here. As work progresses, bugs should be linked here.
Architecture
Memoize and Memcached
Some work has already been done using these technologies to increase the performance of Koha by caching the results of much used subroutines.
mod_perl
The easiest and most effective performance boost for Koha is to make it mod_perl2 safe so that if users want to use mod_perl2 it can be used. Making Koha 3.4 safe for use with mod_perl2 is a major goal.
Supporting Apache::PerlRun is certainly doable, but support for Apache::Registry will take rather more code cleanup. Which are you proposing for 3.4? --- //Galen Charlton 2010/02/10 06:34//
C4::Search
For the most part this module does it job, but it is overly complicated and hard to maintain and change. Refactoring this a major goal.
Circulation performance
XML out of circulation code
One of the big bottlenecks in circulation at present is the constant parsing and writing of XML. Shifting the data needed for circ out of the xml columns and shifting the processing of xml out of the circulation code will speed it up immensely. Henri Damien Laurent has done some work in this area, I will be drawing heavily on his ideas.
It's more general than getting XML out of the circulation code as such - the issue is, more broadly, embedding item data in the bib MARC and MARCXML. Getting it out will also improve performance during cataloging, particularly in the case of serials. It will also resolve an issue where OPAC and staff bib details display fails if a bib has more than a few hundred items attached to it. --- //Galen Charlton 2010/02/10 06:30//
AJAX
Adding AJAX support that fails gracefully is another good potential performance boost
Packaging
Finishing the debian packaging for 3.4 is a major goal. If packages can be created for other distributions that would be great also
Template Toolkit
HTML::Template::Pro has served us well for few years but we are running into limitations with it. Template::Toolkit is under much more active development, is more feature rich and allows for much easier to maintain and translate templates This is a major goal for 3.4
If this is not achieved, we really should apply some patch to change the default HTML::Template::Pro escaping, as in http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3652
Work is well underway on this Template_toolkit_test
Database Abstraction
I would like 3.4 to be installable on both mysql and postgresql with equal ease
Performance and memory Encumbrance
Features
Described in http://wiki.koha-community.org/wiki/Category:Koha_3.4_RFCs