On Sun, January 7, 2007 3:34 pm, Stanislav Malyshev wrote: >> Well a lot of people develop on windows and deploy on Linux with >> mod_php. For these people it probably makes more sense using mod_php >> on >> windows still. > > How it should matter for them - PHP is not supposed to be dependant on > SAPI except for maybe some things in environment variables - which > would > be different on deployment machine anyway?
IIRC, there are 4 things in mod_php that can't be done with CGI, and thus presumably FCGI. [This is my Swiss Cheese memory going back to an exhaustive list I compiled by bugging the crap out of Rasmus back in PHP 3.0 days, so take this whole post with a HUGE grain of salt...] The big one is the HTTP Authentication (?) because, errr, it would have to pass the password in cleartext through a process that would be visible to `ps auxwww` ??? So while it's not technically impossible, it's just verboten in PHP source as a really stupid thing to do. Am I remembering this correctly?... The other 3 are, like, so arcane that only .1% of users even care, as I recall. Some may even be vestigal, like, Hyperwave or somesuch, and could be crossed off the list, if I could find it, in the PHP mailing list archives, from back before the "big split" to PHP-General etc. That said, if my Production environment is mod_php, I want my dev environment to be mod_php, because I'd rather not find out the hard way that it makes some subtle but important difference when I get to QA/staging. If I'm never ever going to be using FCGI in Production, then I really don't want to spend time/money trying FCGI in Development -- And I don't think that's an unrealistic attitude... YMMV -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
