Re: [PHP-DEV] Re: Windows Threads

[Shane Caraveo]

Nick Loman wrote:


Well, that's cool then! Why not simply include all this stuff with PHP
rather than supporting the flawed ISAPI that it currently is packaged
with?


4.3 the windows cgi binary is compiled with fastcgi support.  I'm going 
to be testing the fastcgi on osx this week once I get things building 
correctly, so that should allow easy building of the cgi/fcgi binary on 
osx and linux.

fastcgi itself is not php specific, and is supported from fastcgi.com.

It's not the isapi plugin itself that is at fault, and likely not too 
much of the core is a problem, it is the state of thread safety in the 
extensions and third party libraries that are used in php.  It's also a 
lack of good mt testing facilities.  And for those who dont care about 
isapi, face it, you'll have the same exact problems with apache 2 mpm.

Shane


--
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Re: Windows Threads

[Nick Loman]

Well, that's cool then! Why not simply include all this stuff with PHP
rather than supporting the flawed ISAPI that it currently is packaged
with?


On Thu, 21 Nov 2002, Shane Caraveo wrote:

> John Coggeshall wrote:
> 
> > Shane (and everyone else):
> >
> >
> >
> > >Why don't we move PHP into a separate executable. Design a
> > >"thin" ISAPI DLL which purely passes the data which the ISAPI
> > >DLL exposes between the IIS process and the PHP process (or
> > >process-pool for added reliability). The resulting page is
> > >processed in the application server and returned to the ISAPI
> > >DLL where it is output.
> >
> >
> > Shane and I have already been looking into a similar solution for the
> > UNIX version of PHP. In fact, if you ask'd him I think he's already got
> > something working in this respect using FastCGI. 
> 
> This is exactly what fastcgi does.
> 
> >
> >
> > Incidently, Shane weren't you involved in the Windows port of PHP? :)
> 
> Yes, I am to blame.
> 
> >
> >
> > >I think this solution will be *way* easier than trying to fix
> > >every single bug in PHP so that it is utterly thread-safe and
> > >crash-free.
> >
> >
> > That's the idea. Part of the issue is that the external libraries PHP
> > uses can't be promised to be thread-safe.
> 
> 
> An thus why I did the isapi fastcgi plugin.  www.fastcgi.com
> 
> Shane
> 
> 
> -- 
> PHP Development Mailing List 
> To unsubscribe, visit: http://www.php.net/unsub.php
> 
> 


-- 
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Re: Windows Threads

[Shane Caraveo]

John Coggeshall wrote:


Shane (and everyone else):



>Why don't we move PHP into a separate executable. Design a
>"thin" ISAPI DLL which purely passes the data which the ISAPI
>DLL exposes between the IIS process and the PHP process (or
>process-pool for added reliability). The resulting page is
>processed in the application server and returned to the ISAPI
>DLL where it is output.


Shane and I have already been looking into a similar solution for the
UNIX version of PHP. In fact, if you ask'd him I think he's already got
something working in this respect using FastCGI. 

This is exactly what fastcgi does.




Incidently, Shane weren't you involved in the Windows port of PHP? :)


Yes, I am to blame.




>I think this solution will be *way* easier than trying to fix
>every single bug in PHP so that it is utterly thread-safe and
>crash-free.


That's the idea. Part of the issue is that the external libraries PHP
uses can't be promised to be thread-safe.



An thus why I did the isapi fastcgi plugin.  www.fastcgi.com

Shane


--
PHP Development Mailing List 
To unsubscribe, visit: http://www.php.net/unsub.php