Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 53890 invoked from network); 23 Mar 2009 08:24:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Mar 2009 08:24:58 -0000 Received: (qmail 54092 invoked by uid 500); 23 Mar 2009 08:24:56 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 54041 invoked by uid 500); 23 Mar 2009 08:24:56 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 54033 invoked by uid 99); 23 Mar 2009 08:24:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2009 08:24:56 +0000 X-ASF-Spam-Status: No, hits=4.0 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Mar 2009 08:24:48 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LlfSM-00018g-BG for modperl@perl.apache.org; Mon, 23 Mar 2009 01:24:26 -0700 Message-ID: <22655872.post@talk.nabble.com> Date: Mon, 23 Mar 2009 01:24:26 -0700 (PDT) From: andynic To: modperl@perl.apache.org Subject: mod_perl backward compatibility MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: andynic_nl@yahoo.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm a newbie to much of this. I have Apache 2.2 and Perl 5.10 on my Windows XP computer. I have developed a number of perl scripts using CGI and DBI. I am tempted to try mod_perl so that I can achieve a persistent db connection. My concern is that my existing CGI code will no longer work. Is this a valid concern? Or is a mod_perl configuration backward compatible with existing CGI scripts? Thanks for your help. Andynic -- View this message in context: http://www.nabble.com/mod_perl-backward-compatibility-tp22655872p22655872.html Sent from the mod_perl - General mailing list archive at Nabble.com.