Hi Guys, As a heavy user of ZTS in multi threaded C/C++ applications, here are my $0.02.
Removing ZTS would be a bad idea for all those custom multi-threaded applications out there that allow some form of internal/embedded PHP scripting. These applications are not web-servers but do make use of threads for reasons of their own. Building a FastCGI set-up would be out of the question if these apps are deployed customer / client side and need concurrent PHP script runs. > Based on the feedback on this thread, I think we should instruct users > that using thread-safe versions of PHP is slower, and that actually > putting thread-safe PHP inside a multithreaded server is not a very > reliable solution. We should recommend FastCGI/fpm instead. We should do > that tomorrow morning (figuratively speaking). > Zeev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > This makes a lot of sense, I see where FastCGI/fpm is the best solution for the majority of users of PHP which deploy large scale web applications. The tone in this conversation looked like ZTS had no place in the PHP future. I think it does, but maybe not for the regular web server / web application use case. For custom applications with embedded PHP, I see it making more and more sense as a lot of native applications need to interface with web services and often SDK's for these services are either not available or tedious to use for native application development. Being able to use the PHP SDK's and quickly build conduits between custom apps and services using PHP is very beneficial. Developers of these kind of apps are well aware of the potential pitfalls in using threads and potential non TS libraries as long as documentation is clear about it. My biggest worry is when we signal that ZTS is a relic or not important enough to support in extensions we end up with developers building extensions not trying to be ZTS compatible even if they could be made thread safe easily. For the majority of extensions it's a simple question of adding the TSRM macros. If the underlying library doesn't support it or it would impact performance too much, I would at least want to know that the extension is not thread safe so I can leave it aside and come up with another solution. Bas van Beek -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
