|
|
Posted by John Murtari on 04/07/07 14:25
hansBKK,
>> Yes, thanks for that. It has some of the best information
>> I have found (I was suprised to see I had posted to the thread
>> years ago). It does seem that it just isn't possible and keep
>> 'normal' functionality. I checked the php.net bug tracker and
>> saw a request posted on this, the response was 'will not happen.'
>
> Not so bad running v4 as a module and v5 as CGI, as long as your customers
> can still set their v5 php.ini options as well as v4 .htaccess, no?
>
> Most people coding for 5 should be prepared to deal with a CGI environment
> by now, and the "legacy" people can stick with 4.
Yes, thanks, but as you know running CGI is a lot more server
overhead than as a built in module; also, on our apache server we
use 'suexec' so that user's scripts run under their userid -- that makes
some operations a lot easier (we provide web hosting). PHP runs as
the 'server' so there are some different coding issues especially if
an application wants to upload/create files on the server. If people
got used to a CGI PHP environment, it might not be an easy transition
if it was incorporated as a module.
Because of a wide user base it just makes things simpler
if the environment stays the same (as were able to do in the
php 3 -> php 4 transition).
Best regards!
--
John
___________________________________________________________________
John Murtari Software Workshop Inc.
jmurtari@following domain 315.635-1968(x-211) "TheBook.Com" (TM)
http://thebook.com/
Navigation:
[Reply to this message]
|