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/12/06 00:17:57 UTC
svn commit: r1210701 - in /tcl/rivet/branches/rivet-namespace: ChangeLog
doc/xml/install.xml doc/xml/request.xml
Author: mxmanghi
Date: Mon Dec 5 23:17:57 2011
New Revision: 1210701
URL: http://svn.apache.org/viewvc?rev=1210701&view=rev
Log:
2011-12-06 Massimo Manghi <mx...@apache.org>
* doc/xml/request.xml,doc/xml/install.xml: documenting new configure switches
Modified:
tcl/rivet/branches/rivet-namespace/ChangeLog
tcl/rivet/branches/rivet-namespace/doc/xml/install.xml
tcl/rivet/branches/rivet-namespace/doc/xml/request.xml
Modified: tcl/rivet/branches/rivet-namespace/ChangeLog
URL: http://svn.apache.org/viewvc/tcl/rivet/branches/rivet-namespace/ChangeLog?rev=1210701&r1=1210700&r2=1210701&view=diff
==============================================================================
--- tcl/rivet/branches/rivet-namespace/ChangeLog (original)
+++ tcl/rivet/branches/rivet-namespace/ChangeLog Mon Dec 5 23:17:57 2011
@@ -1,3 +1,6 @@
+2011-12-06 Massimo Manghi <mx...@apache.org>
+ * doc/xml/request.xml,doc/xml/install.xml: documenting new configure switches
+
2011-12-05 Massimo Manghi <mx...@apache.org>
* src/apache-2/mod_rivet.c: child init sets also the array module_conf to signal the
compilation flags --enable-rivet-commands-export and --enable-import-namespace-commands
Modified: tcl/rivet/branches/rivet-namespace/doc/xml/install.xml
URL: http://svn.apache.org/viewvc/tcl/rivet/branches/rivet-namespace/doc/xml/install.xml?rev=1210701&r1=1210700&r2=1210701&view=diff
==============================================================================
--- tcl/rivet/branches/rivet-namespace/doc/xml/install.xml (original)
+++ tcl/rivet/branches/rivet-namespace/doc/xml/install.xml Mon Dec 5 23:17:57 2011
@@ -202,12 +202,20 @@ tar -xvf rivet-X.X.X.tar.gz</programlist
definitions. For compatibility with existing code, commands are exported from
::rivet and can be thus imported into any namespace (global namespace included)
with the command
- <programlisting>
- namespace import -force ::rivet::*
- </programlisting>
+ <programlisting>namespace import -force ::rivet::*</programlisting>
The default value for this option may change in the future.
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>--disable-import-rivet-commands</term>
+ <listitem>
+ Rivet commands can be imported imported into the global namespace. This
+ is done by default and can be disabled using this option. In future
+ versions of Rivet the default will be changed to off and eventually
+ removed altogether.
+ <note>This option implicitly sets --enable-rivet-commands-export</note>
+ </listitem>
+ </varlistentry>
</variablelist>
</para>
<para>
Modified: tcl/rivet/branches/rivet-namespace/doc/xml/request.xml
URL: http://svn.apache.org/viewvc/tcl/rivet/branches/rivet-namespace/doc/xml/request.xml?rev=1210701&r1=1210700&r2=1210701&view=diff
==============================================================================
--- tcl/rivet/branches/rivet-namespace/doc/xml/request.xml (original)
+++ tcl/rivet/branches/rivet-namespace/doc/xml/request.xml Mon Dec 5 23:17:57 2011
@@ -4,18 +4,29 @@
<simplesect>
<title>Apache Child Process Lifecycle</title>
<para>
- Apache responds to HTTP requests through child processes spawned at
- start up. The number of child processes that have to be initially created
+ At startup Apache spawns child processes which are to become the real
+ agents responding to incoming HTTP requests.
+
+ The number of child processes that have to be initially created
can be controlled in the configuration and the optimum choice
for this numbers basically depends on the webserver workload and on the
available system resources. See
<ulink url="http://httpd.apache.org/docs/2.2/misc/perf-tuning.html">Apache
documentation</ulink> for further reading about this crucial point.
- Each of the child process is set up to respond to requests
- that will come from the network accordingly to the configuration
- parameters. If your webserver has been properly configured you will have Tcl
- scripts executed (Rivet templates go through a parsing stage before execution).
- Your web applications will be doing much of their work doing this job of
+ If your webserver has been properly configured you will have Tcl
+ scripts executed (Rivet templates go through a parsing stage before execution)
+ when tcl or rvt files are referenced in one of these cases
+ <itemizedlist>
+ <listitem>The script is explicitly referenced in the URL. E.g.:
+ <programlisting>http://<myserver>/<path-to-script>/<script>.tcl</programlisting></listitem>
+ <listitem>The script is implicitly referenced by rewriting the URL. See:
+ <ulink url="http://httpd.apache.org/docs/current/mod/mod_rewrite.html">mod_rewrite</ulink>
+ documentation</listitem>
+ <listitem>The script is implicitly referenced by
+ <ulink url="http://httpd.apache.org/docs/2.0/mod/mod_alias.html">redirecting or
+ aliasing</ulink> the URL to the real script</listitem>
+ </itemizedlist>
+ Your web applications will be doing much of their work doing this work of
responding to requests and creating content to be sent back to a client.
</para>
<para>
@@ -41,8 +52,9 @@
be served.
</para>
<para>
- <note>This directive has effect when
- <command>SeparateVirtualInterps</command> is off</note>
+ <note>
+ <command>ServerInitScript</command> has effect for child processes when
+ <command>SeparateVirtualInterps</command> is off</note>
</para>
</listitem>
<listitem>
@@ -63,7 +75,7 @@
When <command>SeparateVirtualInterps</command> is turned on
each configured virtual host will have its own slave interpreter.
<command>ChildInitScript</command> is the directive to be
- placed within a <VirtualHost ...> ... </VirtualHost ...>
+ placed within a <VirtualHost...>...</VirtualHost ...>
stanza to have a special initialization of an interpreter bound to
a certain virtual host. This scenario of interpreter
separation is extremely useful to
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-cvs-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-cvs-help@tcl.apache.org