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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
