Re^2: New version of Mod

My site is a high traffic site that uses mod_perl only for the following reasons:
- performance since all code is precompiled
- persistent database connections (DBI is overloaded by Apache::DBI to do this)
- good UTF8 support
- code does not need to be rewritten. It overloads the CGI object

I've considered the following modules:
FCGI: does not support multi-byte chars properly (it is not Unicode aware and only characters within the range 0x00-0xFF are supported)
FastCGI: no persistent database connections. UTF8 support?
Plack: requires refactoring of the code. I couldn't find persistent database connection support in the man pages.

Did I miss a solution? Thank you for your reply. I'm curious to find out about your thoughts.

Comment on Re^2: New version of Mod_perl

Replies are listed 'Best First'.
Re^3: New version of Mod_perl by stonecolddevin (Parson) on Jan 29, 2015 at 21:56 UTC
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	[reply]

Replies are listed 'Best First'.

Re^3: New version of Mod_perl
by stonecolddevin (Parson) on Jan 29, 2015 at 21:56 UTC

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

[reply]