sp Tue Oct 28 10:20:18 2003 EDT
Modified files:
/phpdoc/en/features persistent-connections.xml
Log:
Fixed bug # 26018
-Fixed typos
-Some text changes
Index: phpdoc/en/features/persistent-connections.xml
diff -u phpdoc/en/features/persistent-connections.xml:1.22
phpdoc/en/features/persistent-connections.xml:1.23
--- phpdoc/en/features/persistent-connections.xml:1.22 Tue Sep 2 18:52:27 2003
+++ phpdoc/en/features/persistent-connections.xml Tue Oct 28 10:20:18 2003
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.22 $ -->
+<!-- $Revision: 1.23 $ -->
<chapter id="features.persistent-connections">
<title>Persistent Database Connections</title>
@@ -48,13 +48,10 @@
work of serving up web pages. When each request comes in from a
client, it is handed off to one of the children that is not already
serving another client. This means that when the same client makes
- a second request to the server, it may be serviced by a different
- child process than the first time. What a persistent connection
- does for you in this case it make it so each child process only
- needs to connect to your SQL server the first time that it serves a
- page that makes use of such a connection. When another page then
- requires a connection to the SQL server, it can reuse the
- connection that child established earlier.
+ a second request to the server, it may be served by a different
+ child process than the first time. When opening a persistent connection,
+ every following page requesting SQL services can reuse the same
+ entsablished connection to the SQL server.
</simpara>
<simpara>
The last method is to use PHP as a plug-in for a multithreaded web
