I've also been using cgiwrap for a long time, and I loooove it.

The idea of a cgiwrapped module doesn't really make sense. You need to launch your script with cgiwrap, then it will load your modules and you'll be happy.

Instead of making your application and trying to figure out CGIwrap with it, make a few really simple scripts that test the functionality of CGIwrap. Then, once you've figured out CGIwrap, tackle your application.

Here's what I'd recommend.

Step 1) Make a really dopey whoami script..

#! /usr/bin/perl -w -T
print $<;
[download]

I don't know if that will actually work. You might have to make it generate HTML tags, headers, etc... The important part is that it's a really simple script that only does one thing, which is print your UID.

Step 2) Make a similarly dopey script that reads your config file. Maybe even a shell script, like this:

#! /bin/bash
cat /home/me/myfiles/.config
[download]

When you're making the whoami script work, you might struggle with CGIwrap's funny URL convention. Make sure you understand it before you go any further. For example:

If you have a script at /home/me/myfiles/cgi-bin/woot.pl

You'd have to call it as http://myserver/cgi-bin/cgiwrap/me/woot.pl

Your ISP can customise that, and they might even set up helpers to make it easier... Just make sure you understand it.

Good Luck

--Pileofrogs

The idea of a cgiwrapped module doesn't really make sense. You need to launch your script with cgiwrap, then it will load your modules and you'll be happy.

Bing Bing Bing! Light goes on. Thanks!


—Brad
"The important work of moving the world forward does not wait to be done by perfect men." George Eliot