https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15562
--- Comment #4 from Srdjan Jankovic <[email protected]> --- There's a serious problem with Koha - it is CGI-centric. So all that singleton badness (as in context, database connection, cache) is to make global vars and optimise performance of the existing code under CGI conditions. I think better idea would be an app container, and develop with that in mind, rather then improving existing code base performance and then doing triple somersaults to get it going in modern setups. Even Koha:: namespace is very in line with the one CGI process paradigm. This is an attempt to control the damage while we decide how to move on. The idea is to enable context-less module load, and improve on clunky set_context -> restore context mechanism. I have tried many pages with caching situation, and it seems to work in both old CGI and new plack setup. But I did not go to every corner. I strongly suggest we start moving towards Koha::App container (a persistant glorified context without singletons). -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
