Re: Is mod_perl going the way of the dinosaur?

[hippo]

Short answer: no.

Longer answer: mod_perl is used to embed a perl interpreter into Apache and this allows for the creation of filters and handlers in Perl. That's an awesome feature and it's the only way to do this. However, BitD mod_perl was sold on the efficiency benefits of a persistent dynamic server so a large number of less well-informed people thought that this was the only reason to use it. With the advent of FastCGI, PSGI, etc. this becomes less of a reason to use mod_perl so that segement of the user base has generally migrated away. The core who use it for other purposes remain.

FastCGI, no longer downloadable from some servers (phased out already), seems to be promoted here; but I am left wondering where one obtains it?

From https://httpd.apache.org/download.cgi#mod_fcgid

A friend wants to run my scripts on his Windows computer.

Your friend might benefit from some persuasion regarding their choice of operating system ;-)

If you your friend really wants to run anything on MSWin32, they will probably require help specific to that O/S - at which point I am happy to leave the two of you to it. Best of luck!

[Polyglot]

I would tell my friend just to use the online versions of my scripts, but he is working with tribes up in the mountain regions where they have very poor cellular reception and no internet. He comes into town once in awhile and catches up with friends online before going back "out of contact." He needs my scripts to do some of his work--and he'll need to synchronize his work with the online server from time to time if others are to benefit by it (and if he is to have a good backup of it).

The link you provided looked vaguely familiar--sure enough, I'd been there already. There is no working make/cmake/nmake/gmake... on the Windows computer, so even this fastcgi option fails to install. In trying to use one of the 'make' options, I've seen errors including anything from not finding the apxs executable to having a recursive path (infinite loop) in the directory tree which stopped the process. Many, many "file not found" type of errors, in most cases of which the files actually exist on the system (not the case for the apxs executable).

It's been a good reminder for why I left Windows and never looked back. My friend claims he's forced by certain pieces of equipment into the Windows mold, as there are no Mac drivers for them. I certainly did promote Mac over Windows while he was here. Sadly, some are hard to persuade.

[etj]

Strawberry Perl used to supply dmake, and now supplies gmake. Using that might at least solve the lack of a make.