When you say cgi vs. php, I'm going to assume you mean cgi versus apache module (correct me if I misunderstand). To be honest I don't know enough about the internals of the apache module to tell you why it's better for an apache server (would love it if someone could explain!). What I do know I've gathered from PHP's site... check these out:
http://www.php.net/install.commandline http://us3.php.net/manual/en/security.cgi-bin.php
Jason
[original post]
hi..
a really general/basic question... what is the difference between a "cgi" app and a php app.. does it really come down to where the app is being run from..
i mean within apache, if i specify that php/perl/etc... app resides at a given location, and that files with a certain extension are to be handled by the perl/php/etc app, then i can handle the processing of the file by the interpreter anywhere within my site that i grant access to. is there anything/any reason to have a "cgi-bin" portion of my app, other than good design practice...
clarification would be useful!!!
thanks..
-bruce
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
