RE: [PHP4BETA] 4.0 B3 RC 3 - output.c

Andi wrote: >We were actually thinking of nuking the non-TS version as it adds a bit of >maintenance overhead and our aim is for people to use it as an ISAPI >module and not CGI binary on Win32. In any case there shouldn't be more than one project covering any non-trivial amount of code. If necessary, continuing to support multiple configurations within a project is a possibility, but I would recommend against it unless there were an *extremely* compelling reason as such choices tend to grow exponentially. Hopefully there is nothing to preclude a php4/sapi/apache/apache.dsp from being written... Personally, I love the CGI version for debugging... >TS adds some overhead but with the overhead of CGI the kind of projects >using it would probably not suffer from the slight performance decrease of >TS. From what I have seen, I can't imagine that it would be noticable. Peter wrote: >As of beta 3 rc 3 the ISAPI DLL and php_mssql DLL don't work together >correctly. I haven't had a chance to try to debug it, but I know that the >CGI version with MS SQL works fine, and the ISAPI version alone works fine. >The TS version builds a CGI executable just fine. This is independent of TS vs non-TS, right? In other words, if php4dll.dsp were eliminated, you can still build a working CGI version of MS SQL with php4ts.dsp, right?