As far as the future direction of embedded PHP (and let's agree here
we aren't talking about every application, for mass vhosters some
fcgi or suid flavor of PHP is going to remain a better choice, and
for others, so we can avoid that debate)...
The next direction for server worker pools will likely be a threadless
connection; while waiting for your POST body the php engine environment
will most efficiently be parked and resumed on another thread. (Some
code has been started in this direction at httpd although there are
no corresponding 'engine' hacks yet for embedded language systems.)
So although the new patches look great for a threading application,
keep in mind that a more traditional zts mode may be worthwhile to
retain.
Hi,
As far as the future direction of embedded PHP (and let's agree here
we aren't talking about every application, for mass vhosters some
fcgi or suid flavor of PHP is going to remain a better choice, and
for others, so we can avoid that debate)...The next direction for server worker pools will likely be a threadless
connection; while waiting for your POST body the php engine environment
will most efficiently be parked and resumed on another thread. (Some
code has been started in this direction at httpd although there are
no corresponding 'engine' hacks yet for embedded language systems.)So although the new patches look great for a threading application,
keep in mind that a more traditional zts mode may be worthwhile to
retain.
The patch, if it is included, does not remove the current ZTS mode ;)
However the current mode does not guaranties that PHP will work if a request
is started in a thread and continued in an other. If support for that is added
in the future (TSRM already has a set of functions to allow that), this can
work with the patch too.
Regards,
Arnaud