> -----Original Message----- > From: Douglas Kirkland [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 10, 2003 12:43 PM > To: [EMAIL PROTECTED] > Subject: Re: [cgiapp] CGI-Simple vs. CGI.PM > > > On Tuesday 10 June 2003 09:29 am, Neil Mansilla wrote: > > >�But I thought CGI-Application 'automatically' used CGI. I nowhere > > >have a > 'use CGI;. So how > > >�would I make CGI::Application use CGI-Simple? > > > > > >�Kind regards, > > > > > >�gerard > > > > I second Gerard's request -- how do you do this? �And, my second > > question is what type of shortfalls can I expect to find? �In other > > words, are there any other CGI.pm functions used by > CGI::Application > > that may break if I use CGI-Simple (or even say, CGI::Minimal)? > > > > Thanks, > > Neil > > I will put a third request. But from Bob's testing It does > not seem that > important now. > > Douglas > I am unsure. The only test that they come close in is the "new process" one. The one passing data around seems to show "simple" being much faster.
CGI::Simple passes ALL the tests for the areas that it is meant to replace CGI.pm. To clarify CGI::Simple (from perldoc): CGI::Simple provides a relatively lightweight drop in replacement for CGI.pm. It shares an identical OO interface to CGI.pm for parameter parsing, file upload, cookie handling and header generation. This module is entirely object oriented, however a complete functional interface is available by using the CGI::Simple::Standard module. Essentially everything in CGI.pm that relates to the CGI (not HTML) side of things is available. There are even a few new methods and additions to old ones! If you are interested in what has gone on under the hood see the Compatibility with CGI.pm section at the end. --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
