You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tcl.apache.org by mx...@apache.org on 2019/01/16 17:40:57 UTC

[tcl-rivet] 03/03: manual pages corrections and improvements

This is an automated email from the ASF dual-hosted git repository.

mxmanghi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tcl-rivet.git

commit a280718ea5a94724693b1007c0802829d275ae60
Author: Massimo Manghi <mx...@apache.org>
AuthorDate: Wed Jan 16 18:40:39 2019 +0100

    manual pages corrections and improvements
---
 doc/rivet.xml          |  2 +-
 doc/rivet.xml.in       |  2 +-
 doc/xml/internals.xml  | 13 +++++++------
 doc/xml/processing.xml |  3 ++-
 4 files changed, 11 insertions(+), 9 deletions(-)

diff --git a/doc/rivet.xml b/doc/rivet.xml
index 3022a6b..a4fe95e 100644
--- a/doc/rivet.xml
+++ b/doc/rivet.xml
@@ -37,7 +37,7 @@
     <!ENTITY formbroker.xml        SYSTEM "xml/formbroker.xml" >
     <!ENTITY version	           	  "3.2" >
     <!ENTITY fullversion           "3.2.0" >
-    <!ENTITY version2-series	     "2.0,2.1,2.2,2.3" >
+    <!ENTITY version2-series	     "2.0,2.1,2.2,2.3,2.4" >
     <!ENTITY version2-generic	     "2.x" >
     <!ENTITY version30		        "3.0" >
     <!ENTITY version31		        "3.1" >
diff --git a/doc/rivet.xml.in b/doc/rivet.xml.in
index 2772fab..4cda7bb 100644
--- a/doc/rivet.xml.in
+++ b/doc/rivet.xml.in
@@ -37,7 +37,7 @@
     <!ENTITY formbroker.xml        SYSTEM "xml/formbroker.xml" >
     <!ENTITY version	           	  "@INIT_VERSION@" >
     <!ENTITY fullversion           "@PACKAGE_VERSION@" >
-    <!ENTITY version2-series	     "2.0,2.1,2.2,2.3" >
+    <!ENTITY version2-series	     "2.0,2.1,2.2,2.3,2.4" >
     <!ENTITY version2-generic	     "2.x" >
     <!ENTITY version30		        "3.0" >
     <!ENTITY version31		        "3.1" >
diff --git a/doc/xml/internals.xml b/doc/xml/internals.xml
index 146e185..6e0083d 100644
--- a/doc/xml/internals.xml
+++ b/doc/xml/internals.xml
@@ -59,13 +59,13 @@
     	<para>
     		A bridge is a loadable library implementing different ways to handle
     		specific features needed to mod_rivet. It was originally meant as a way
-    		to handle the prefork/worker/event MPM specificities that prevented mod_rivet
-    		from supporting each of them, at the same time avoiding the need to stuff the 
+    		to handle the prefork/worker/event MPM specificities, at the same time 
+    		avoiding the need to stuff the 
     		code with conditional statements that would have implied useless complexity (an
     		instance of the Apache web server can run only an MPM at a time), 
     		error prone programming and performance costs. 
     		New bridges could be imagined also to implement different models of workload
-    		and resource management (like the resources demanded by the Tcl interpreters). 
+    		and resource management (like the resources demanded by the Tcl interpreters).
 			We designed an interface between the core of mod_rivet and its MPM bridges 
 			based on a set of functions defined in the rivet_bridge_table structure. 
     	</para>
@@ -82,10 +82,11 @@
 				<listitem>
 					<emphasis>mpm_server_init</emphasis>: pointer to any
 					specific server inititalization function. This field can be NULL
-					if no bridge specific initialization has to be done. The core of
+					if no bridge specific initialization is needed. The core of
 					mod_rivet runs the <command>ServerInitScript</command> before
-					calling this function.</listitem>
-					<listitem><emphasis>mpm_child_init</emphasis>: Bridge specific
+					calling this function.
+				</listitem>
+				<listitem><emphasis>mpm_child_init</emphasis>: Bridge specific
 					child process initialization. If the pointer is assigned with
 					a non-NULL value the function is called by Rivet_ChildInit. 
 				</listitem>
diff --git a/doc/xml/processing.xml b/doc/xml/processing.xml
index 763e922..a218094 100644
--- a/doc/xml/processing.xml
+++ b/doc/xml/processing.xml
@@ -77,7 +77,8 @@
 			which provides a very basic interface for both initialization
 			and request processing. Such script will be sourced into the
 			Tcl interpreter at the mod_rivet initialization stage. In the
-			Apache configuration (most likely within a &lt;VirtualHost myrivetapp.com:80&gt;...&lt;/VirtualHost&gt;
+			Apache configuration (most
+			likely within a &lt;VirtualHost myrivetapp.com:80&gt;...&lt;/VirtualHost&gt;
 			definition block)
 		</para>
 		<programlisting>&lt;IfModule rivet_module&gt;


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@tcl.apache.org
For additional commands, e-mail: commits-help@tcl.apache.org