20 Dec
2013
20 Dec
'13
10:09 a.m.
Le 18/12/2013 23:36, Galen Charlton a écrit : > Hi, > > On Wed, Dec 18, 2013 at 8:28 AM, Paul Poulain > <paul.poulain@biblibre.com> wrote: >> Le 10/12/2013 23:50, Brendan Gallagher a écrit : >>> Finishing the Plackifying of the staff-side so that it could be >>> stably used. >> The SAN-OP is running Plack on staff since 3.10, it runs fine, >> except for C4/BackgroundJobs, and we could not understand where the >> problem comes from, because we can't reproduce it outside from >> SAN-OP server (which is expected to be a >> Wheezy-with-nothing-exotic) > > I think there may be a bit more to it considering the existence of > things like bug 9224 and the lack of a consensus Plack configuration > in the source tree. That's what I should have pointed: there's some/quite a lot of work to do to setup Plack during install if we want. Next question then: what do we want : * the installer let the user choose Plack - CGI mode ? (ie: trading memory for performance) * the install is made in CGI mode and we provide tools to setup Plack for those who want it (manually editing configurations) * the install is made in CGI mode and we document how to setup Plack * other idea ? > That said, I would agree that Plack-compatibility for the staff > interface is both achievable and not far off for 3.16. and give a good benefit. Added to caching & DBIx::Classing (with cache too), the performance gain will be large (on the long term) -- Paul POULAIN - Associé-gérant Tel : (33) 4 91 81 35 08 http://www.biblibre.com Logiciels Libres pour les bibliothèques et les centres de documentation