From 13df64d2dc964366c6c2e06e8b0b28575fd75194 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Johannes=20Schl=C3=BCter?= Date: Wed, 7 Apr 2010 13:43:19 +0000 Subject: [PATCH] Zend Extension != PHP Extension (zend module) .. try to aovid some confusion git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@297616 c90b9560-bf6c-de11-be94-00142212c4b1 --- internals2/structure/lifecycle.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/internals2/structure/lifecycle.xml b/internals2/structure/lifecycle.xml index 37ce44daae..7c5912aad8 100644 --- a/internals2/structure/lifecycle.xml +++ b/internals2/structure/lifecycle.xml @@ -4,7 +4,7 @@ Life cycle of an extension - A Zend extension goes through several phases during its lifetime. All of + A PHP extension goes through several phases during its lifetime. All of these phases are opportunities for the developer to perform various initialization, termination, or informational functions. The Zend API allows for hooks into five separate phases of an extension's existence, apart from @@ -18,7 +18,7 @@ As the Zend engine runs, it processes one or more "requests" from its client. In the traditional CGI implementation, this corresponds to one execution of a process. However, many other implementations, most notably - the Apache module, can map many requests onto a single PHP process. A Zend + the Apache module, can map many requests onto a single PHP process. A PHP extension may thus see many requests in its lifetime.