Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: unknown (asf.osuosl.org: error in processing during lookup of
 apreq-dev-list@2xlp.com)
Mime-Version: 1.0 (Apple Message framework v750)
Content-Transfer-Encoding: 7bit
Message-Id: <16DC4BC8-04EB-4C3E-9505-120385988C1C@2xlp.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: apreq-dev@httpd.apache.org
From: Jonathan Vanasco <apreq-dev-list@2xlp.com>
Subject: perl glue usage style question
Date: Wed, 31 May 2006 18:40:45 -0400

this is a style question for using the perl glue, purely stylistic -  
just wondering what the accepted standard is in terms of accessing a  
param within a single cgi script

ie: access the param via $libapreq every time, or pull 1x, then use  
repeatedly

this is a halfassed illustration below showing some exceedingly poor  
design ideas.  just trying to show exxagerated scenarios.


case a:
	sub aa {
		if ( $request->param('a') eq 'b' ){
			do_stuff( $request->param('a') );
		}
		more_stuff( $request->param('a') );
		other_stuff( $request->param('a') );
		different_stuff();
	}
	sub different_stuff{
		if ( $request->param('a') eq 'b' ){
		}
	}

case b:
	sub aa {
		if ( $a eq 'b' ){
			do_stuff( $a );
		}
		more_stuff( $a );
		other_stuff( $a );
		different_stuff();
	}
	sub different_stuff{
		if ( $request->param('a') eq 'b' ){ # or rewrite to accept $a as an  
arg like the others
		}
	}