[pm-h] Looking for PSGI web server Daemon
Michael R. Davis
mrdvt92 at yahoo.com
Fri Jun 26 13:52:44 PDT 2015
Perl Folks,
I just want to keep you in the loop on my PSGI experimentation. So, I think I've settled on Fast CGI under Apache. For me it's best as I can simply reuse our APR authentication session layer and not have to worry about authentication in the application layer. So, I did examples connecting to our databases in Plack, Dancer, Catalyst, and Mojolicious::Lite. I like Mojolicious::Lite the best so far as it is designed the way I "think". I like Dancer but its not RPMs friendly so, it's just too much to build all of the RPMs to get to a deployment ready solution. Mojolicious is RPM ready, however, deployment with Mojolicious::Lite is biting me as I have not figured out how to add a prefix yet. Development with Starman URLs are like /this/:id but under Apache Fast CGI they are /path/this/:id. I use DBIx::Array::Connect for all of our databases (100s of them) and Mojolicious::Lite will let me just do it without hassle. So, issues that I'm still facing: Mojolicious::Lite - Deployment path is different than development path and I need to figure out how to handle that. - How to handle database stale connections and connection timeouts (I assume that I'll have to move to DBIx::Connection wrappers for all database connections.) - die() sends HTML I need it to send JSON... There has got to be an easy way. PSGI/FCGI is very interesting with a *lot* of performance advantages over CGI. Persistent memory (e.g. database connections) is the hardest part to get used to.Thanks,Mike mrdvt92
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/houston/attachments/20150626/e0e5d7f0/attachment.html>
More information about the Houston
mailing list