Re: RFC: unicode.semantics: runtime or not?
| From: | Sean Coates | Date: | Wed, 06 Sep 2006 16:46:31 +0000 |
| Subject: | Re: RFC: unicode.semantics: runtime or not? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25538@lists.php.net to get a copy of this message | ||
> 1. ZEND_INI_SYSTEM and make people run two copies of Apache if they want
> both modes. This is architecturally more simple and more robust, I believe.
> 2. ZEND_INI_PERDIR and let people switch modes as described above. This
> is a lot of work and will probably result in quite a few edge cases
> where we used to rely on stability of one mode (such as APC or
> serialization, for example).
I agree that #1 is more robust, and altogether simpler.
However, I think that this will heavily affect the PHP 6 adoption
rate... especially for virtual hosters. If, for example,
register_globals had no PERDIR/per-vhost capability, I'd _still_ have
applications that I couldn't run (... mostly from cvs.php.net).
Therefore, from an end-user/sysadmin standpoint, I'd have to go with #2.
S