You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-cvs@tcl.apache.org by da...@apache.org on 2002/10/15 17:24:19 UTC
cvs commit: tcl-site/presentations/apache-tcl future.gif left.gif logo.gif requestflow.gif right.gif common.tcl current_products.ttml presentation.tex servingpages.ttml style.css
davidw 2002/10/15 08:24:19
Modified: presentations/apache-tcl common.tcl current_products.ttml
presentation.tex servingpages.ttml style.css
Added: presentations/apache-tcl future.gif left.gif logo.gif
requestflow.gif right.gif
Log:
Added .gif files in order to convert presentation to PDF via automated
tool which doesn't support PNG.
Revision Changes Path
1.3 +2 -2 tcl-site/presentations/apache-tcl/common.tcl
Index: common.tcl
===================================================================
RCS file: /home/cvs/tcl-site/presentations/apache-tcl/common.tcl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- common.tcl 10 Oct 2002 02:52:19 -0000 1.2
+++ common.tcl 15 Oct 2002 15:24:18 -0000 1.3
@@ -53,13 +53,13 @@
<table align="center" width="90%">
<tr>
<td align="left">
- <a href="[prevurl]"><img src="left.png" alt="previous"></a>
+ <a href="[prevurl]"><img src="left.gif" alt="previous"></a>
</td>
<td align="center">
$title
</td>
<td align="right">
- <a href="[nexturl]"><img src="right.png" alt="next"></a>
+ <a href="[nexturl]"><img src="right.gif" alt="next"></a>
</td>
</tr>
</table>
1.2 +1 -1 tcl-site/presentations/apache-tcl/current_products.ttml
Index: current_products.ttml
===================================================================
RCS file: /home/cvs/tcl-site/presentations/apache-tcl/current_products.ttml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- current_products.ttml 10 Oct 2002 02:52:19 -0000 1.1
+++ current_products.ttml 15 Oct 2002 15:24:18 -0000 1.2
@@ -12,7 +12,7 @@
projects, and is moving towards having 3, or less, in the future.
<p align="center">
- <img src="future.png" alt="">
+ <img src="future.gif" alt="">
</p>
<?footer?>
</body>
1.3 +44 -45 tcl-site/presentations/apache-tcl/presentation.tex
Index: presentation.tex
===================================================================
RCS file: /home/cvs/tcl-site/presentations/apache-tcl/presentation.tex,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- presentation.tex 11 Oct 2002 15:29:12 -0000 1.2
+++ presentation.tex 15 Oct 2002 15:24:18 -0000 1.3
@@ -232,13 +232,13 @@
\includegraphics[scale=0.6]{./future.ps}
Getting ahead of ourselves, our short term plans are to release Rivet,
-and phase out mod\_dtcl and NeoWebScript. Long term, if possible, we
-will further modularize all our offerings, so that at some point, it
-would be possible to run Rivet and Websh as loaded packages from
-within mod\_tcl, as it is capable of giving us low level access to the
-Apache internals from Tcl. So, we wouldn't really only have one
-project, but there would be, at the same time, more modularity and
-tighter integration amongst the remaining systems.
+and phase out mod\_dtcl and NeoWebScript. Our long term goals, should
+they come to fruition, are to further modularize all our offerings, so
+that at some point, it would be possible to run Rivet and Websh as
+packages loaded from within mod\_tcl, as it is capable of giving us
+low level access to the Apache internals from Tcl. So, we wouldn't
+really only have one project, but there would be, at the same time,
+more modularity and tighter integration amongst the remaining systems.
Without further ado, our 5 projects are:
@@ -252,7 +252,7 @@
with mod\_dtcl as its basis in late 2000.
mod\_dtcl will eventually be replaced by Apache Rivet, which is
- infact, getting just about 100\% of our development time lately.
+ in fact, getting just about 100\% of our development time lately.
The original design goals of mod\_dtcl were based on observations
about the success of PHP, and sought to borrow the best of that
@@ -277,10 +277,10 @@
of exposing the Apache API in Tcl, in order to make it possible to
write Apache modules in Tcl. Most of the other projects take
advantage of Apache features, and are tightly linked to the server,
- but could conceivably also independent of Apache. mod\_tcl takes
- the opposite approach and gives you access to a great deal of
- Apache's C API. This flexibility means that, one day, other Apache
- Tcl modules might conceivably just be plugins for mod\_tcl.
+ but could conceivably also operate independently of Apache.
+ mod\_tcl takes the opposite approach and gives you access to a great
+ deal of Apache's C API. This flexibility means that, one day, other
+ Apache Tcl modules might just be plugins for mod\_tcl.
\item Websh\\
Websh was born in 1995 as a C++ library incorporating a Tcl
@@ -296,8 +296,8 @@
creating pages.
One unique feature of Websh is that it is relatively independent of
- Apache, and, infact, version is provided that runs as a stand-alone
- CGI.
+ Apache, and, in fact, a version is provided that runs as a
+ stand-alone CGI.
\item Apache Rivet\\
The most recent of the Apache Tcl projects, Rivet is the future of
@@ -323,16 +323,16 @@
This example shows us several features of Tcl. In reality, the Tcl
code used here is entirely generic. The only thing that tells us that
-it is used in Rivet, are the $<$? and ?$>$
-delimiters that indicate that the particular section of the file
-should be parsed as Tcl code, and not HTML. The table (see below)
-which results from this code is created by the two for loops, which
-set and then increment their respective variables. The value used to
-determine the shade of gray for a particular cell is calculated by the
-\textbf{expr} command, and is in turn used in the \textbf{format}
-command, which sets up both the bgcolor to use for the cell. Note
-that the numbers to be displayed in the cell are interpolated directly
-in the string, and are not handled by the format command.
+it is used in Rivet, are the $<$? and ?$>$ delimiters that indicate
+that the particular section of the file should be parsed as Tcl code,
+and not HTML. The table (see below) which results from this code is
+created by the two \textbf{for} loops, which set and then increment
+their respective variables. The value used to determine the shade of
+gray for a particular cell is calculated by the \textbf{expr} command,
+and is in turn used in the \textbf{format} command, which sets up both
+the bgcolor to use for the cell. Note that the numbers to be
+displayed in the cell are interpolated directly in the string, and are
+not handled by the format command.
\includegraphics[scale=1.0]{./table.ps}
@@ -405,22 +405,22 @@
options are also available to control file upload characteristics, as
well as determine whether separate virtual hosts get their own
interpreters. This last feature is particularly important in
-environments where separate clients might want to have their own tcl
+environments where separate clients might want to have their own Tcl
code, loaded separately.
\subsection{How Rivet Serves Pages}
-When tracing through the Rivet code to find out how it works when a
-Rivet page (.rvt) is requested from the Apache server, the module
-checks to see if a cached version of the page's bytecode is available.
-If it isn't, the page is read into memory, and parsed into a script,
-which is then executed, as well as stored in the cache. If it is
-available in cache, the script is executed directly, without having to
-touch the disk at all to reload it. Naturally the cache size is
-configurable via an Apache directive. The parser works by
-transforming chunks of HTML - everything outside of the $<$? ?$>$ tags -
-into large \textbf{puts} statements, which can then be executed along
-with the rest of the Tcl code as one large script.
+When a Rivet page (.rvt) is requested from the Apache server via HTTP,
+after passing through Apache, the module checks to see if a cached
+version of the page's bytecode is available. If it isn't, the page is
+read into memory, and parsed into a script, which is then executed, as
+well as stored in the cache. If it is available in cache, the script
+is executed directly, without having to touch the disk at all to
+reload it. Naturally the cache size is configurable via an Apache
+directive. The parser works by transforming chunks of HTML -
+everything outside of the $<$? ?$>$ tags - into large \textbf{puts}
+statements, which can then be executed along with the rest of the Tcl
+code as one large script.
\subsection{Tcl Channels}
One of the especially interesting things about the Rivet
@@ -466,15 +466,14 @@
This is another topic that merits hours of discussion on its own, so
we are going to stick with a few highlights that have been of
-particular help.
+particular help to us as when working with Apache code.
It would be hard not to talk about ``pools'', which are Apache's
-memory management system for modules, which is extremely convenient
-for the module author. Pools take care of freeing memory after you
-have used it for tasks during the request (well, at other points too,
-but we are aiming for a simple talk!). There are also lots of
-convenient string functions that take advantage of pools to make life
-easier
+memory management system for modules, and are very convenient for the
+module author. Pools take care of freeing memory after you have used
+it for tasks during the request (well, at other points too, but we are
+aiming for a simple talk!). There are also lots of convenient string
+functions that take advantage of pools to make life easier
It's not part of Apache proper but the apreq code is very useful for
handling data received from users - cookies, GET and POST variables.
@@ -497,7 +496,7 @@
different, flexible, multipurpose systems - is a testament to the
strength and adaptability of both Tcl and Apache.
-More information is availabile at the following sites:
+More information is available at the following sites:
\begin{itemize}
\item http://www.tcl.tk - The Tcl web site.
1.3 +1 -1 tcl-site/presentations/apache-tcl/servingpages.ttml
Index: servingpages.ttml
===================================================================
RCS file: /home/cvs/tcl-site/presentations/apache-tcl/servingpages.ttml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- servingpages.ttml 11 Oct 2002 07:09:53 -0000 1.2
+++ servingpages.ttml 15 Oct 2002 15:24:18 -0000 1.3
@@ -24,7 +24,7 @@
</ul>
<p align="center">
- <img src="requestflow.png" alt="">
+ <img src="requestflow.gif" alt="">
</p>
<?footer?>
1.4 +2 -1 tcl-site/presentations/apache-tcl/style.css
Index: style.css
===================================================================
RCS file: /home/cvs/tcl-site/presentations/apache-tcl/style.css,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- style.css 11 Oct 2002 07:09:53 -0000 1.3
+++ style.css 15 Oct 2002 15:24:18 -0000 1.4
@@ -1,3 +1,4 @@
+
body {
font-family: Arial, sans-serif;
font-style: normal;
@@ -9,7 +10,7 @@
body.splash {
font-size: 300%;
- background: url(logo.png);
+ background: url(logo.gif);
}
1.1 tcl-site/presentations/apache-tcl/future.gif
<<Binary file>>
1.1 tcl-site/presentations/apache-tcl/left.gif
<<Binary file>>
1.1 tcl-site/presentations/apache-tcl/logo.gif
<<Binary file>>
1.1 tcl-site/presentations/apache-tcl/requestflow.gif
<<Binary file>>
1.1 tcl-site/presentations/apache-tcl/right.gif
<<Binary file>>
---------------------------------------------------------------------
To unsubscribe, e-mail: tcl-site-cvs-unsubscribe@tcl.apache.org
For additional commands, e-mail: tcl-site-cvs-help@tcl.apache.org