Plack should act as a middleware between your code and the web server, there shouldn't really be much need for refactoring. In fact, it looks like it already has a handler: https://metacpan.org/pod/Plack::Handler::Apache2. Sorry, this is going the other way, plack -> mod_perl. Regardless, I think the Plack documentation mentions somewhere about routing everything properly through Plack to your existing mod_perl app code: https://metacpan.org/pod/PSGI::FAQ#I-have-a-CGI-or-mod_perl-application-that-I-want-to-run-on-PSGI-Plack.-What-should-I-do
In terms of persistent database connections, I'm not sure how this is tied to mod_perl. However, I recommend looking at DBIx::Connector as it has a lot of really good connection logic built into it while still being "just DBI".
Three thousand years of beautiful tradition, from Moses to Sandy Koufax, you're god damn right I'm living in the fucking past
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
