internals:extensions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
internals:extensions [2013/04/10 12:54] – jpauli | internals:extensions [2013/04/10 13:28] – jpauli | ||
---|---|---|---|
Line 264: | Line 264: | ||
It checks the extension field '' | It checks the extension field '' | ||
Note that conflicts requirements have already been checked against, at extension loading (see last chapter) | Note that conflicts requirements have already been checked against, at extension loading (see last chapter) | ||
- | After that, '' | + | After that, the extension globals are registered (call to '' |
+ | |||
+ | ==== Activating Zend extensions ==== | ||
+ | Zend extensions are then activated **after** PHP extensions | ||
+ | zend_extension_startup() is called on the Zend extensions registry | ||
+ | | ||
+ | '' | ||
+ | Dont be fooled here, it's not the '' | ||
+ | |||
+ | ===== Extensions lifetime ===== | ||
+ | You may know PHP's lifetime. Very basically, '' | ||
+ | We already detailed php_module_startup() previously, to show how both PHP extensions and Zend extensions live into this stage. | ||
+ | |||
+ | ==== Request startup ==== | ||
+ | Zend extensions come first, and their '' | ||
+ | PHP extensions come second, and their '' | ||
+ | |||
+ | ==== Request shutdown ==== | ||
+ | PHP extensions come first, and their '' | ||
+ | Zend extensions come after, and their '' | ||
+ | A third hook is called : '' | ||
+ | |||
+ | ===== Main schema ===== |
internals/extensions.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1