Hi!
> I did not check latest ICU code base but we never had any issues in
> intl in ZTS. However you are right, since 5.3.0 most TS issues were in
One of them has to do with number formatting, so if you have a number of
apps that use different locale settings on the same server, which have
different number separators, you may encounter it. Not a frequent use
case, though. See: http://bugs.icu-project.org/trac/ticket/6711
Not unique to TS, but there might be ones that are, if they use globals
in this manner. Just showing that modern libraries are still having this
kind of issues, and it's very hard to get maintainers to fix them.
> I never said fcgi performs badly. What I say is that Windows design is
> not process based, none of the hiperformence tools available on this
> platform is based on threads (AD, IIS, asp.net, etc.).
ITYM based or processes, or s/none/all/. But so what? For IIS case
threads are fine, but for our case - shared-nothing - they don't help us
much. No idea what asp.net does but they probably designed it to be
threaded from scratch, so it probably has very different architecture
than PHP.
> Filesystem is getting better, it is already better in 5.3.0+ and will
> be a bit better in 5.5.0 (if I got the time to do it :/). We do not
> use the unicode API yet (for IO or FS), so no real impact yet but a
> few functions that still have to use it in some libs or in core.
AFAIR all APIs that go into filesystem, C library, etc. ultimately end
up with Unicode - i.e.
> To bring zts in line with NTS in term of performance is possible, look
> at Arnaud's 1st draft for a TLS support in php:
>
> https://wiki.php.net/rfc/tls
TLS is nice, I have nothing against TLS, and if somebody wants to get
behind the effort to get ZTS to use TLS, great. But I was talking about
cost of setting up envt for PHP script, which is not going to change.
You need to initialize all the globals, create all the structures, etc.
etc. - it's all not free.
> The IIS pipeline architecture allows much more than only auth, much more.
I know, it's just an example. I'm just saying PHP request init is
expensive, and I'm not even sure we can do proper init on early stages
of IIS request... So PHP may not be the best thing to use inside IIS
pipeline in general case.
> ease the developer work and reduce the wtf factors. TLS is one of
> them.
Fine, so who's going to do this? This RFC is marked with 2008, now it's
2013 and it didn't happen. Why?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227