in reply to CGI.pm vs. CGI modules

I suggest checking out CGI::Application. It makes creating a complex cgi app a lot easier, and has hooks into HTML::Template. The more I use it, the more awkward it seems when I'm not using it.

Replies are listed 'Best First'.
Re: Re: CGI.pm vs. CGI modules
by rruiz (Monk) on Oct 17, 2002 at 23:54 UTC

    Yes, the moment I read about CGI::Application on the post My experiences using CGI::Aplication... by scazat, I realized it was a great module. Unfortunately, my host provider does not have it installed, I will be looking into the posibilities for them to install both modules, but mean while I need to analyse the best path to make my CGI's using the modules they have already installed.

    Also a big thank you very much for you and for everybody else for your comments in this node. ;)

      Note that if you can upload scripts, you can also install modules, pure-Perl ones at least. Just fetch the tarball, install it locally to some subdirectory, upload that to your host, and use lib in the script to point at the path they can be found at before you use the modules in question.

      Makeshifts last the longest.

        Good point, I will look into this approach as a temporal testing solution while the modules get installed at the server. Thank you for pointing this out.