Module activation order in php_request_startup()
| From: | Moriyoshi Koizumi | Date: | Wed, 29 Dec 2004 04:56:37 +0000 |
| Subject: | Module activation order in php_request_startup() | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-14229@lists.php.net to get a copy of this message | ||
Hi,
Currently activation functions are called in the following order
on request startup:
1. zend_activate()
2. sapi_activate()
3. php_hash_environment()
4. zend_activate_modules()
Is there any good technical reason behind this order? I don't think
it does make much sense because php_hash_environment() can call
input handlers before the modules providing those handlers are
initialised.
It also resulted in a fatal bug in mbstring reported recently
in the Japanese user's mailing list; some settings kept in the
module globals leak over requests.
Regards,
Moriyoshi