RE: [INTERNALS-WIN] RE: [PHP-DEV] Differences in VC6 and VC9 Windows builds and MSSQL Driver.

Hi Pierre,

> > I think we should do some announcement to the SAPI maintainers to ask
> them
> > to check their modules with their servers (if the SAPI is available for
> > Windows).
> 
> We did, you were the last one :) And you know it now (as we discussed
> that already before about the nsapi support in 5.3 and now here :)

Hrrrrrm, missed the mail (maybe because I was not on this list). Sorry!
Currently I have much to do for two other OS projects, so I do not have all
may time for NSAPI :)

> The other sapi are either dead (p3web) or not compatible (thttpd,
> etc.). Apache will be apache2 only (apache1 on windows never worked
> well and is now unmaintained).
> 
> ISAPI should be kept, however we may disable it before 5.3.0-final but
> leave the sources in place for 3rd parties (there is a discussion on
> this list about that). FastCGI is the supported SAPI for IIS these
> days (by php or MSFT), as it works way better than ISAPI.
> 
> > For NSAPI, I will do this some time in future (low priority),
> > because it is some work to install a windows server and add SJSWS 7.0 to
> it
> > and possibly debug it (if it does not work). SJSWS is not able to run on
> my
> > local Win XP Prof (I am not sure about this, maybe it works, I will give
> it
> > a try).
> 
> I'm not sure testing the NSAPI on XP makes any sense. You may test it
> on 2k3 or 2k8 instead :)

It is enough to test, if runtime linking works correctly and for that the
operating system is not so important. :-)

But I have a Win2003 server somewhere running IIS, I will install a SJSWS in
parallel for testing. I inform you about the results, maybe I contact Chris
Elving from Sun again to ask him about usage of VC9 in the next server
version (7.1,....). And Sun plans to release SJSWS for the open source
community some time in future, this may make things simplier.

For Solaris, Sun supplies prepackaged PHP with FastCGI and NSAPI modules
(you can choose during installation). They have now a howto page comparing
NSAPI and FastCGI, and they recommend FastCGI for overloaded PHP
installations with thread unsafe libs (with the drawback of not be able to
support customized error pages powered by PHP, more complicated rewrite
support, no virtual(),...), and NSAPI for all other cases where the
performance of this fantastic [my opinion] server is needed (e.g. I have a
sol server running MediaWiki with rewritten URIs, Contenido CMS, DIGIR and
our developments) with lots of hits per second perfectly running thread safe
with NSAPI (really *no* crashes).

Uwe