Let me try and be more accurate and understandable.

There's a difference between "slow and horrible" and incorrect. You're not doing anything incorrectly! :)
The set up you have with Plack::Handler::Apache2 is correct but not optimal and has its disadvantages. If you can do it differently (such as having persistency) it will be more worthwhile.

The deployment document was mostly written by the community and contains practical information about situations people encountered, sometimes without any ability to change it. Our most recommended set up is Varnish <-> Nginx <-> Starman <-> Dancer. However, sometimes you're using Apache, sometimes you don't have a reverse proxy, sometimes you don't have caching up front, sometimes you can't run a Perl webserver (like Starman). These are all limitations you might face, and the deployment procedure tries to help you with that.

On Thu, Aug 16, 2012 at 5:14 PM, gurugeek <gurugeekphp@gmail.com> wrote:


On Thu, Aug 16, 2012 at 3:37 PM, sawyer x <xsawyerx@gmail.com> wrote:
The reason you don't need restarts is because it loads everything on every request, like with CGI. That's slow and horrible. mod_perl has startup.pl[1] which helps deal with it, and on the Plack::Handler::Apache2[2] there's an example in the synopsis on handling the same thing[3].


I see well I am using what is available in the guide at 
http://search.cpan.org/dist/Dancer/lib/Dancer/Deployment.pod
 

_______________________________________________
Dancer-users mailing list
Dancer-users@perldancer.org
http://www.backup-manager.org/cgi-bin/listinfo/dancer-users