Comments on: The Rise and Fall of mod_perl

By: Randolf Richardson

Randolf Richardson — Tue, 01 Mar 2011 20:07:55 +0000

***UPDATE***

There’s a new release of mod_perl2 now (just last month in February 2011, I believe), which hopefully resolves these Windows issues.

By: Randolf Richardson

Randolf Richardson — Wed, 06 Oct 2010 08:46:34 +0000

Mike B: Thanks for that helpful link. I see that there are pre-compiled Windows binaries for mod_perl2 there, along with libapreq2 (which I also use with my mod_perl2 projects).

I’ve played around with Strawberry Perl a few times, but couldn’t get mod_perl2 compiled before. Now that these pre-compiled modules available, I can start to look at Strawberry Perl seriously.

By: Mike B

Mike B — Wed, 15 Sep 2010 11:38:15 +0000

I guess I ran into similar issues, when I was using a mod_perl that was originally compiled for ActiveState and use that with Strawberry.

Since some time now, kmx managed to compile mod_perl with the StrawberryPerl build tools and this seems to work reliably, for me at least. You might want to check this out:

http://strawberryperl.com/package/kmx/mod_perl/

By: Randolf Richardson

Randolf Richardson — Mon, 16 Aug 2010 06:30:20 +0000

I’ve experienced different sorts of issues with mod_perl2 on Windows, and after getting everything resolved I found that some of the problems came back on a 64-bit Windows 7 system.

Specifically, the problem I’ve not been able to resolve is to get DBD::Pg to load at all, even in Perl from the command-line (so I know it’s not a mod_perl2-specific issue).

On Unix (I use NetBSD primarily for all my production servers), all these annoying little problems that crop up at various unexpected times simply never come to light on Unix.

You might consider running VirtualBox.com on your Windows system to get the benefits of the Unix side of things running there. Heck, you can even mount an SMB resource into the web portion of your virtualized Unix system if you like, and then your developers won’t even notice that you’re transparently proxying all your .pl files to a virtualized system.

The solution you found is interesting, especially because of the scalability factors. Thanks for posting such an interesting article.

By: Mark

Mark — Tue, 18 May 2010 04:49:16 +0000

I’ve really enjoyed reading your pieces related to CGI-ish frameworks in Perl, and your take on exception handling. It’s been very helpful as I look at various options myself, running into similar concerns.

Thanks for taking the time to do this, and in a way that reveals your exploration and questions along the way. And yes, the Perl people don’t blog enough, it seems.

By: Interesting Perl Links – 2010 Week 14 « A Curious Programmer

Interesting Perl Links – 2010 Week 14 « A Curious Programmer — Wed, 07 Apr 2010 10:09:02 +0000

[...] talks about using the catalyst dev server on Windows / Strawberry Perl due to problems with building mod_perl. Interestingly one of the [...]

By: Adam Taylor

Adam Taylor — Mon, 15 Mar 2010 15:08:59 +0000

I could be wrong here but I thought that Stardust was a port of Unicorn, which is [apparently] decidedly unixy [1].

[1] http://tomayko.com/writings/unicorn-is-unix

By: Florian Ragwitz

Florian Ragwitz — Tue, 09 Mar 2010 02:34:49 +0000

I’m glad to see you resolved your issues.

I understand the that Engine::HTTP::Prefork doesn’t work on Win32. However, we also got an Engine::Plack, and Plack itself has a variety of server backends, like Stardust, Twiggy, which are probably less unix specific than Prefork and could have a better chance of running on Windows, without having to use Catalyst’s development-only server.