Plack is not a module. It’s a namespace. Letting apache manage your app directly for you is a mistake on at least two levels (restarts are tied to the webserver and all process management is static and also tied to webserver; plus server errors can hang a process in the server for as long as the timeout setting which *must* be long or else cromulent responses will be cut off as errors when slow) which is why I suggested FastCGIExternalServer. And wait… you’re telling everyone there is a plackup command? You know I published a rather long set of PSGI stuff with links to relevant packages earlier showing what you’re hand waving about and ended the tour with usage of plackup.
Please post supporting code, configuration, or links if you have anything to add.
| [reply]
[d/l]
[select] |
As you point out, this very definitely does have a lot to do with precisely how the CGI app is structured. For example, there really are some sites out there which define a bunch of independent (Perl) scripts ... instead of a single “application” ... and, although they technically do “work,” this approach is really not compatible with FastCGI.
Balooney, doesn't matter over how any files its spread, its as compatible with fastcgi as anything else
| [reply] |
| [reply] |