in reply to CGI modules?

For really lightweight things, I liked CGI::Request, but that seems to have disappeared from the world (except when bundled with other packages). It has the same interface as CGI but doesn't have the extra cruft. It looks like CGI::Lite has taken over that spot. If you want to do vanilla CGI insetead of mod_perl stuff, you won't be able to use Apache::Request.

--
brian d foy <brian@stonehenge.com>
Subscribe to The Perl Review

Replies are listed 'Best First'.
Re^2: CGI modules?
by Copper Maiden (Acolyte) on Jan 28, 2006 at 22:16 UTC
    Thanks for all the replies. I guess I'll go for CGI::Lite. But assuming the server does have mod_perl, is Apache::Request any faster?

    BTW, I'm making a web app and I'm trying to make it somewhat portable. So I might still end up using CGI.pm, or even worse, writing it in PHP.
[reply]

      Well, mod_perl is a lot faster because you don't have to start perl over and over again. If you decide to use mod_perl later, options such as PerlRun will still make your scripts pretty quick without having to change anything.

      --
      brian d foy <brian@stonehenge.com>
      Subscribe to The Perl Review
[reply]
        Hi, I was wondering here about other persistent options which use some external process which is started once only (the RPC idea all again...); pperl is one interesting possibility, but it does not build on HP-UX for example (I hope to make it work by changing the fd passing code)... so I am afraid pperl is not a portable solution. Are there any matures ones?
[reply]

In Section Seekers of Perl Wisdom