I’ve been trying out a few things in mod_perl just recently, getting together a small basic framework that handles sessions and generates an entire site (apart from images) from a bunch of Perl modules. It’s a lot harder than I thought it would be but I’ve got the basic code working now.
Next step is security of session data.
Updated my network programming tutorial to answer a question that someone emailed me about it. Tried to compile the library on my mac last night and found that half the makefile was wrong, some of the includes didn’t exist on OSX and that you have to use ranlib on the .a file as well as using ar to create it.
Maybe one day I’ll actually finish it or maybe amend it to include Perl examples as well.
Having installed MySQL for OSX from Apple’s UNIX & Open Source downloads section and Server Logistics, I found that the Perl module DBD::mysql wouldn’t compile and install. The solution it seems is to compile it by hand (oh, the horror!)
Doh! It seems that Apache::Template (the mod_perl interface for Template Toolkit and a cool looking module) isn’t compatible with mod_perl 1.99 and Apache 2.0.x.
Having had a chance to read through most of the new Template Toolkit book from O’Reilly, I have to admit that it’s far more impressive than I first realised. Extra plugins and filters can be written and added into the basic templating system to provide extra functionality that doesn’t come as standard.
It’s just typical. I wait a couple of months for the new Template Toolkit book from O’Reilly to appear on Safari (the online bookshelf) and then when I give in and buy the paper copy it appears on Safari a few days later.
I’ve been looking at alternatives for storing Perl structures within a database such as MySQL. Here are the main contenders: