Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7DFDA200D5A for ; Thu, 30 Nov 2017 01:40:30 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7C7F1160C17; Thu, 30 Nov 2017 00:40:30 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C3DDF160C04 for ; Thu, 30 Nov 2017 01:40:29 +0100 (CET) Received: (qmail 63904 invoked by uid 500); 30 Nov 2017 00:40:28 -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 63894 invoked by uid 99); 30 Nov 2017 00:40:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2017 00:40:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 28FD7C3E21 for ; Thu, 30 Nov 2017 00:40:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.2 X-Spam-Level: X-Spam-Status: No, score=0.2 tagged_above=-999 required=6.31 tests=[KB_WAM_FROM_NAME_SINGLEWORD=0.2, KHOP_DYNAMIC=0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qE5zoYcyX1Ka for ; Thu, 30 Nov 2017 00:40:27 +0000 (UTC) Received: from cope.tawonga.bunyatech.com.au (ppp59-167-189-60.static.internode.on.net [59.167.189.60]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 56F4A5F4EB for ; Thu, 30 Nov 2017 00:40:25 +0000 (UTC) X-Clacks-Overhead: GNU Terry Pratchett Received: from DHCP.tawonga.bunyatech.com.au (DHCP.tawonga.bunyatech.com.au [10.0.1.78] (may be forged)) (authenticated bits=0) by cope.tawonga.bunyatech.com.au (8.15.2/8.15.2/MSA) with ESMTPSA id vAU0eF1L007250 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for ; Thu, 30 Nov 2017 11:40:16 +1100 (AEDT) (envelope-from bscott@bunyatech.com.au) Subject: Re: CGI module deprecation To: modperl@perl.apache.org References: <86mv34bxfe.fsf@red.stonehenge.com> <3f52ab8e-17c5-400e-c8f4-2eb3b0f82bef@cablewholesale.com> From: Brian Scott Message-ID: <5d5169c6-1c3e-f7d6-fb27-4256afce9b01@bunyatech.com.au> Date: Thu, 30 Nov 2017 11:40:17 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <3f52ab8e-17c5-400e-c8f4-2eb3b0f82bef@cablewholesale.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Content-Language: en-US archived-at: Thu, 30 Nov 2017 00:40:30 -0000 I've just put a system together with CGI::Simple and everything seemed to behave properly. I seem to recall other CGI.pm compatible things out there as well when I was looking around. CGI::Simple seems to be working well enough that at some point I might go back and tweak some old stuff that uses CGI. I haven't verified the speed or size claims but it's working well on an old Raspberry-Pi (very low volumes) so can't be too bad. It claims to be 100% compatible on the parsing side with all the html stuff removed. I haven't pushed very hard to verify this. Brian On 30/11/17 8:27 am, Michael A. Capone wrote: > "and uses the CGI module only for parsing the incoming request." > > I was going to follow up on this thread and ask for suggestions on > what I could/should use for incoming request parsing.� I have never > gone further in mod_perl beyond Apache::Registry and just running > traditional CGI programs, and I only use CGI.pm to get the request > parameters (but I use it a LOT).� Is there another modeule that I can > drop in to get that functionality?� Or should I happily keep using > CGI.pm (which I have no problem installing from CPAN as long as it's > available). > > On 11/29/2017 01:13 PM, Randal L. Schwartz wrote: >> My CGI::Prototype is still in use by one of my primary clients, and uses >> the CGI module only for parsing the incoming request.� The rest is a >> nice prototype-inheritance structure of Template Toolkit objects. >> >> print "Just another Perl hacker,"; >> >