Commit cd7d40b8 authored by stolpmann's avatar stolpmann

Doc bugs pointed out by David Mentre.


git-svn-id: https://godirepo.camlcity.org/svn/wdialog/trunk@215 f54c9a64-0731-4a92-b797-30fd5898f27c
parent 4302dc6b
......@@ -4592,7 +4592,22 @@ In order to run the application as CGI, call the function
startup can be reduced by using <code>wd-xmlcompile</code>, however.
</ul>
</blockquote>
]]></html></p>
]]></html>
<latex>
\fbox{\begin{minipage}{14cm}
{\large\bf Summary for CGI}
\begin{itemize}
\item Execution model: New process for every page request, and the process must
initialize everything from the very beginning
\item Advantages: The processes are isolated from each other, so malfunction of
one process does not interfer with the other concurrently running processes.
Resources of the operating system are guaranteed to be deallocated.
\item Disadvantages: Long initialization time. The time needed for WDialog
startup can be reduced by using {\tt wd-xmlcompile}, however.
\end{itemize}
\end{minipage}}
</latex>
</p>
</sect2>
<sect2><title>FastCGI</title>
......@@ -4767,7 +4782,23 @@ after the maximum period of time has expired.</p>
can block the whole application.
</ul>
</blockquote>
]]></html></p>
]]></html>
<latex>
\fbox{\begin{minipage}{14cm}
{\large\bf Summary for JSERV, Sequential execution}
\begin{itemize}
\item Execution model: A single process gets the requests one after another.
Requests arriving while the current request is being processed must wait
in a queue.
\item Advantages: Minimal overhead to resolve concurrency. The activations
for the requests can share data.
\item Disadvantages: There is no isolation between the activations, and there
is no automatic clean-up strategy to close files. Very long activations
can block the whole application.
\end{itemize}
\end{minipage}}
</latex>
</p>
</sect3>
......@@ -4810,7 +4841,23 @@ way to let the activations share data or other resources.
data or other resources.
</ul>
</blockquote>
]]></html></p>
]]></html>
<latex>
\fbox{\begin{minipage}{14cm}
{\large\bf Summary for JSERV, Forking execution}
\begin{itemize}
\item Execution model: The already initialized main process spawns for every
incoming request a new subprocess that performs the remaining work.
\item Advantages: The processes are isolated from each other, so malfunction of
one process does not interfer with the other concurrently running processes.
Resources of the operating system are guaranteed to be deallocated.
The initialization time per request is quite short but not negligible.
\item Disadvantages: It is difficult to arrange that the activations share
data or other resources.
\end{itemize}
\end{minipage}}
</latex>
</p>
</sect3>
......@@ -4857,7 +4904,23 @@ know.</p>
implemented to start or stop processes as needed.
</ul>
</blockquote>
]]></html></p>
]]></html>
<latex>
\fbox{\begin{minipage}{14cm}
{\large\bf Summary for JSERV, Process\_pool execution}
\begin{itemize}
\item Execution model: The already initialized main process spawns a fixed
number of worker processes, and every worker runs sequentially.
\item Advantages: The initialization time per request is very low.
\item Disadvantages: The activations for the requests are not isolated from
each other, but it is also difficult to let them share data. There is
no automatic deallocation of resources of the operating system.
As a restriction of the possibilities of the model, it is currently not
implemented to start or stop processes as needed.
\end{itemize}
\end{minipage}}
</latex>
</p>
</sect3>
......@@ -5238,7 +5301,7 @@ Certain indexes to the defines names.
(including CGI), and all process models.</p></li>
<li><p>It maintains session state even if the application
crashes, or needs to be restarted.</p></li>
<li><p>It performs session garbage collection in parallel which
<li><p>It performs session garbage collection in parallel with
the application, and is therefore usually faster than the
memory session manager.</p></li>
</ul>
......@@ -5259,7 +5322,7 @@ Certain indexes to the defines names.
uses the daemon. This is done in the wdstated.conf file, which
is included with the distribution. These credentials ensure that
session data is only available to authorized applications. Next
you should start wdstated as an unprivlidged user. You can pass
you should start wdstated as an unprivileged user. You can pass
the location of the config file as an argument to wdstated if it
fails to find it. In your application, create an instance of
<c>Wd_daemon_session.daemon_session_manager</c>, and pass it to
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment