Re: [PHP] what functionality does CGI miss in relation to apache module SAPI?
On Tue, April 18, 2006 5:26 pm, Jochem Maas wrote: > CGI is the only way to run php5 on an apache setup already running the > php4 module (the guy the admins the server in question will only > install > php5 in that way because it's managable -- that is to say Gentoo now > support > this configuration via their emerge system) Well... Maybe you could get them to implement what RASMUS said was the "right way" to do this... :-) You'll have to search the archives for it, from about 6 months (?) ago... It was pretty slick, and wouldn't hurt their 4.x userbase at all. At least, it SEEMED pretty slick, but I didn't really fully understand it... :-^ -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] what functionality does CGI miss in relation to apache module SAPI?
Richard, thanks for the feedback. Richard Lynch wrote: On Tue, April 18, 2006 3:54 am, Jochem Maas wrote: does anyone have a concise list of the functionality missing from the CGI SAPI in comparison to the the Apache module (including any functional differences)? as far as I can tell CGI doesn't give me anything extra in terms of functionality but the precise differences elude me (STFW didn't turn up any difinitive info - that might a be monday morning issue, combined with a lack of coffee) I know I once tracked down all four (4) things in PHP 3 that wouldn't "work" with CGI and posted to the PHP list. There was only one list back then... I think one was the HTTP Authentication, because the username/password would have to be passed on the command line to the CGI. Or *something* that would have required passing a password on the command line, so it was disabled for that reason, and HTTP Authentication is the obvious candidate. O*#@(&%)(#285 [EMAIL PROTECTED]&^#%@ *#%#*%(@ now I'm having a really bad day. HTTP Auth is one of the things I need. IIRC, the other functions were s esoteric, there wasn't any real reason to prefer CGI/Module in terms of "feature set" other than HTTP Auth, but that was long ago, so there may be more functionality now that matters. If you have a really GOOD reason to use CGI, you probably will not notice any features "missing". If you do, almost for sure a quick read of the docs on php.net will tell you WHY that feature is missing from CGI, even if you can't find a single-page collection of those features. CGI is the only way to run php5 on an apache setup already running the php4 module (the guy the admins the server in question will only install php5 in that way because it's managable -- that is to say Gentoo now support this configuration via their emerge system) .. and I need php4 for the main site that already runs their - it doesnt work with php5 ... and the code is too large and shitty to consider upgrading it. Performance under CGI can suck, or not, depending, as I understand it: *IF* all your Apache children and enough PHP CGI processes can "fit" in RAM without page-faulting, then it's fine. Once your PHP CGI starts getting dumped to disk for page-faults, performance goes bad fast. here Im lucky - the php5 stuff I want to run is meant for CMS/Intranet stuff that is onyl run by the client - so minimal hits to the server (just a couple of employees will be logging in and doing stuff) This is just a parrot of what has been posted here in the past. your parrots are better than most peoples insights my friend! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] what functionality does CGI miss in relation to apache module SAPI?
On Tue, April 18, 2006 3:54 am, Jochem Maas wrote: > does anyone have a concise list of the functionality > missing from the CGI SAPI in comparison to the the Apache > module (including any functional differences)? as far as I can > tell CGI doesn't give me anything extra in terms of functionality > but the precise differences elude me (STFW didn't turn up > any difinitive info - that might a be monday morning issue, > combined with a lack of coffee) I know I once tracked down all four (4) things in PHP 3 that wouldn't "work" with CGI and posted to the PHP list. There was only one list back then... I think one was the HTTP Authentication, because the username/password would have to be passed on the command line to the CGI. Or *something* that would have required passing a password on the command line, so it was disabled for that reason, and HTTP Authentication is the obvious candidate. IIRC, the other functions were s esoteric, there wasn't any real reason to prefer CGI/Module in terms of "feature set" other than HTTP Auth, but that was long ago, so there may be more functionality now that matters. If you have a really GOOD reason to use CGI, you probably will not notice any features "missing". If you do, almost for sure a quick read of the docs on php.net will tell you WHY that feature is missing from CGI, even if you can't find a single-page collection of those features. Performance under CGI can suck, or not, depending, as I understand it: *IF* all your Apache children and enough PHP CGI processes can "fit" in RAM without page-faulting, then it's fine. Once your PHP CGI starts getting dumped to disk for page-faults, performance goes bad fast. This is just a parrot of what has been posted here in the past. -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] what functionality does CGI miss in relation to apache module SAPI?
hi Guys/Girls, does anyone have a concise list of the functionality missing from the CGI SAPI in comparison to the the Apache module (including any functional differences)? as far as I can tell CGI doesn't give me anything extra in terms of functionality but the precise differences elude me (STFW didn't turn up any difinitive info - that might a be monday morning issue, combined with a lack of coffee) (I'm not interested in any security pro/cons atm) thanks & regards, Jochem -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php