My own approach was to use CGI::Application. The advantage I found was that a) support for HTML::Template is built-in, thus allowing me to use any template design I want. b) I can create a super-class that can auto-magically take care of session and user management each time one of my scripts runs. Basically it looks like this:

script.cgi:

use MySite::SubClass;

my $webapp = MySite::SubClass->new();
$webapp->run();
[download]

MySite::SubClass:

package MySite::SubClass;

use MySite::SuperClass;

sub setup {
    # setup runmodes and script specific stuff
    # ...templates perhaps?
}

# …
# runmodes subs and whatnot :)
# …

1;
[download]

MySite::SuperClass:

package MySite::SuperClass;

use base 'CGI::Application';
use CGI;
# other modules here..

sub cgiapp_init {
    my $self = shift;
    
    # create database handler
    # do session management
}

sub teardown {
    my $self = shift;
    
    # dbh->disconnect
}

# …
# other functions
# …

1;
[download]

You can then create MySite::SubClass2 (etc…) which all use MySite::SuperClass and thus have session management taken care of.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.