On 7/30/07, Dodger <[EMAIL PROTECTED]> wrote: > You're being semantically picky with this guy, and innacurately so. > An apache registry script *is* a CGI script. So is an ASP page, a PHP > script, and any other interpreted way fo dealing with CGI input.
We tend to be generous with the use of the word "CGI" around here, but technically, if it isn't using the CGI protocol as exemplified by mod_cgi, it isn't CGI. People often run PHP through CGI, but when they use mod_php it's not CGI. ASP is not able to run as CGI. > CGI stands for 'Common Gateway Interface and describes the method of > transferring information to a form to the server. That's actually HTTP. CGI defines how the server runs the program on the server, by forking a program and passing things through ENV and STDIN. We don't do that in mod_perl, although we sometimes fake it so that legacy code can still work. > The guy also obviously most likely has mod_perl because he is using the > PerlModule directive in his conf *and* because he's using a startup.pl file. He may have it compiled in, but may not be running any of his scripts through it, in which case Apache::DBI won't work for him. The questions Clinton asked are relevant to figuring out how to help him, and I don't see any bad intentions there. - Perrin
