Why should it be an CGI? Can't you get away with simply isolating the code that is common to both CGI scripts into one (or more) subroutine(s) in a module that can be called by both scripts?
Just my 2 cents, -gjb-
| [reply] |
| [reply] [d/l] |
If you can install other modules, you may want to take a look at this node that explains the use of the CGI::Application module.
That way you may take all of your current CGI scripts and pack them in run modes of your main C::A module.
God bless you rruiz
Update: Corrected link format error found by VSarkiss, thanks
| [reply] |
You could probably just require the other cgi script. This will run the other cgi script, then return to the main cgi.
It looks like there is probably a better way to do what you want. gjb's idea looks like a good way to go. | [reply] [d/l] |
Probably best to encapsulate the required subroutine in a module and use it. If you mean that a certain user action requires two completely seperate CGI transactions you could open a sub window, or sub frame at the client end, or do something whizzy like using a mod_perl handler to generate multiple apache sub requests at the server.rdfield | [reply] |