http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 --- Comment #4 from Paul Poulain <paul.poulain@biblibre.com> --- (In reply to comment #3)
I don't believe that we should wed Koha to Plack as a Fast CGI tool anymore than we should be wedded to MySQL as our database. If we aim to implement PSGI as our standard, we'd have Koha working on Plack, FastCGI or mod_perl, which would let the institution doing the hosting choose how to set up their machines. That's a valid point. OTOH I think we must *highly* improve our authentification workflow (read: rewrite it completely ;-) ) So if we can find a solution for that ...
As for keeping CGI... I'm not sure whether we need to or not, if we've got a good selection of PSGI options that can run on a wide range of hardware. So long as the move away from CGI doesn't disenfranchise anyone running Koha on an older or low-spec machine, I think it could be okay.
well= I have absolutely no doubts that Koha+Plack will work *better* on low-spec machines than in CGI ! 1 thread, keep alive for 30 requests means, according to dobrika, 60MB On a low-spec machine, the number of Plack threads can be limited to 3 or 2 instead of 6, to reach a low memory consumption. (I don't count the plack itself here. Dobrika, if you can give us numbers... -- You are receiving this mail because: You are watching all bug changes.