http://www.perlmonks.org?node_id=1031245


in reply to Re: Perl Modules - Mod_Perl and CGI
in thread Perl Modules - Mod_Perl and CGI

This node was taken out by the NodeReaper on Apr 30, 2013 at 07:09 UTC
  • Comment on Reaped: Re^2: Perl Modules - Mod_Perl and CGI

Replies are listed 'Best First'.
Re^3: Perl Modules - Mod_Perl and CGI
by Trihedralguy (Pilgrim) on Apr 30, 2013 at 03:56 UTC
    What he is saying seems true and is the case when I'm most frustrated. Restarting Apache fixes the problem. What I'm hoping to discover is a solution to turn of the caching on the development machine, so that I can quickly make changes without having to restart or "refresh constantly" to un-cache an error.

      What I'm hoping to discover is a solution to turn of the caching on the development machine, so that I can quickly make changes without having to restart or "refresh constantly" to un-cache an error.

      Um, if you don't want a persistent process, with all the benefits it brings, run it as CGI :/

      OTOH, how tightly is your module/app coupled with Apache? you can always develop with plackup/Plack::Middleware::Refresh / Plack::Loader::Shotgun for faster reloading :)

      What he is saying seems true and is the case when I'm most frustrated.

      Sorry , but it isn't. He said if you change the Perl code, you must restart Apache. which is obviously false (hello Apache2::Reload) because like Apache2::Reload like reloads stuff