Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: Passing variable to another CGI.pm program

by blue_cowdawg (Monsignor)
on Nov 27, 2012 at 16:24 UTC ( #1005878=note: print w/ replies, xml ) Need Help??


in reply to Passing variable to another CGI.pm program

Why pass the name? Use the UID that you are going to glean from /etc/password.

Better yet why not just put the functionality of both CGI scripts into one CGI? This method is a good example of a justification to create modules.

Update: I'm not a big fan of "pipe-fitting" processes together. I remember inheriting a project that suffered from performance issues what consisted of scriptA --pipe--> scriptB --pipe--> scriptC --> and nausuem and back to scriptA types of chains. First thing I did was create modules with the working "guts" of all the scripts and replaced all the scripts. Now if scriptA needed some functionality in scriptB it could access that functionality locally rather than piping.


Peter L. Berghold -- Unix Professional
Peter -at- Berghold -dot- Net; AOL IM redcowdawg Yahoo IM: blue_cowdawg


Comment on Re: Passing variable to another CGI.pm program

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1005878]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (12)
As of 2014-12-23 04:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (135 votes), past polls