Looking at Plack::Handler::Apache2, your app now runs under mod_perl.

As I assume that your PSGI application is more or less a raw PSGI application, returning [200, {}, ["Hello World"]], maybe you have Apache set up to restart the httpd after each request, which is great for debugging.

The easiest way to better confirm that your program is not run as a separate process would be some shared state between requests:

my $counter= 1;

warn "(Re)initializing application $0\n";

return sub {
    [200, {}, ["Hello request " . $counter++]]
};
[download]

If you cannot make $counter++ increase and constantly see the "(Re)initializing" message in your webserver error log, your webserver is running each request in a separate request.

You should get really different behaviour by using plackup with (for example) the Twiggy, Tatsumaki or another in-process backend.

Thanks, that was very helpful.

The thing I'd missed was the instructions to preload the app, using a script:

# Optionally preload your apps in startup
  PerlPostConfigRequire /etc/httpd/startup.pl
[download]

As for going for another back end, that's a whole other thing I figure I'll get to next. All I know is Apache and a little bit of nginx, don't know where to start.

I was and i'm still intersted in the topic: you may like to read Re: Change cgi script to PSGI app and Serving multiple Plack apps
I also have other links on my homenode (..mmh that is a bit chaotic..)

L*

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

I usually use one of the other server types for development, as they make process control much easier to me.

Running one of the other server types behind an Apache or nginx reverse proxy is also possible, but requires much more setup.

This article (http://perlhacks.com/2016/01/easy-psgi/) was on the latest Perl Weekly. Looks like another good resource.