You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rivet-dev@tcl.apache.org by mx...@apache.org on 2011/03/24 15:19:44 UTC

svn commit: r1084965 - /tcl/rivet/trunk/doc/xml/request.xml

Author: mxmanghi
Date: Thu Mar 24 14:19:44 2011
New Revision: 1084965

URL: http://svn.apache.org/viewvc?rev=1084965&view=rev
Log:
third draft of a new section about namespaces and rivet directives finished

Modified:
    tcl/rivet/trunk/doc/xml/request.xml

Modified: tcl/rivet/trunk/doc/xml/request.xml
URL: http://svn.apache.org/viewvc/tcl/rivet/trunk/doc/xml/request.xml?rev=1084965&r1=1084964&r2=1084965&view=diff
==============================================================================
--- tcl/rivet/trunk/doc/xml/request.xml (original)
+++ tcl/rivet/trunk/doc/xml/request.xml Thu Mar 24 14:19:44 2011
@@ -149,7 +149,7 @@
 			assume that the state of a transaction spanning several pages 
 			can be saved in this way and be safely available to a specific client. 
 			Sessions exist for this purpose and Rivet ships its own 
-			<xref href="session_package" /> with support for most of popular DBMS. 
+			session package with support for most of popular DBMS. 
 			Storing data in the global namespace can be useful (and even then scoping 
 			in an application namespace is recommended) when it comes to I/O channel,
 			database connection which are usually specific to a process or other 
@@ -160,7 +160,7 @@
 			A special role in the interpreter is played by the <command>::request</command> 
 			namespace.	The <command>::request</command> namespace is deleted and recreated
 			at every request and Rivet templates (.rvt files) are executed within it. So,
-			unless your fully qualifying variable names outside the <command>::request</command> 
+			unless you're fully qualifying variable names outside the <command>::request</command> 
 			namespace, every variable and procedure created in .rvt files is by default place in
 			it and deleted before any other requests gets processed. It is therefore safe to
 			create variables or object instances in template files and foresake about them: Rivet
@@ -168,7 +168,20 @@
 			is so destroyed.
 		</para>
 		<table>
-			<textobject>tttttttt</textobject>
+			<thead>
+				<td>Stage</td><td>Script</td><td>Namespace</td>
+			</thead>
+			<tbody>
+				<tr><td>Apache Initialization</td><td>ServerInitScript</td><td>::</td></tr>
+				<tr><td rowspan="2">Child Initialization</td><td>GlobalInitScript</td><td>::</td></tr>
+				<tr><td>ChildInitScript</td><td>::</td></tr>
+				<tr><td rowspan="5">Request Processing</td><td>BeforeScript</td><td>::</td></tr>
+				<tr><td>.rvt</td><td>::request</td></tr>
+				<tr><td>.tcl</td><td>::</td></tr>
+				<tr><td>AfterScript</td><td>::</td></tr>
+				<tr><td>AfterEveryScript</td><td>::</td></tr>
+				<tr><td>Child Exits</td><td>ChildExitScript</td><td>::</td></tr>
+			</tbody>
 		</table>
 	</simplesect>
 </section>
\ No newline at end of file



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