~ubuntu-branches/ubuntu/trusty/libapache2-mod-rivet/trusty

</p><div class="section" title="Initialization"><div class="titlepage"><div><div><h3 class="title"><a name="idp9596400"></a>Initialization</h3></div></div></div><p style="width:90%">

</p><div class="section" title="Initialization"><div class="titlepage"><div><div><h3 class="title"><a name="idp5238704"></a>Initialization</h3></div></div></div><p style="width:90%">

When Apache is started, (or when child Apache processes are

started if a threaded Tcl is used),

<code class="function">Rivet_InitTclStuff</code> is called, which

executes Rivet's <code class="filename">init.tcl</code>. The caching

system is also set up, and if there is a

<span style="font-family:monospace"><span class="command"><strong>GlobalInitScript</strong></span></span>, it is run.

</p></div><div class="section" title="RivetChan"><div class="titlepage"><div><div><h3 class="title"><a name="idp9582848"></a>RivetChan</h3></div></div></div><p style="width:90%">

</p></div><div class="section" title="RivetChan"><div class="titlepage"><div><div><h3 class="title"><a name="idp5282528"></a>RivetChan</h3></div></div></div><p style="width:90%">

The <span class="structname">RivetChan</span> system was created in

order to have an actual Tcl channel that we could redirect

standard output to. This lets us use, for instance, the

Tcl's regular standard output is replaced with an instance of

this channel type, so that, by default, output will go to the

web page.

</p></div><div class="section" title="The global Command"><div class="titlepage"><div><div><h3 class="title"><a name="idp9646640"></a>The <span style="font-family:monospace"><span class="command"><strong>global</strong></span></span> Command</h3></div></div></div><p style="width:90%">

</p></div><div class="section" title="The global Command"><div class="titlepage"><div><div><h3 class="title"><a name="idp5284144"></a>The <span style="font-family:monospace"><span class="command"><strong>global</strong></span></span> Command</h3></div></div></div><p style="width:90%">

Rivet aims to run standard Tcl code with as few surprises as

possible. At times this involves some compromises - in this

case regarding the <span style="font-family:monospace"><span class="command"><strong>global</strong></span></span> command. The

you really need a true global variable, use either

<span style="font-family:monospace"><span class="command"><strong>::global</strong></span></span> or add the :: namespace qualifier

to variables you wish to make global.

</p></div><div class="section" title="Page Parsing, Execution and Caching"><div class="titlepage"><div><div><h3 class="title"><a name="idp9652080"></a>Page Parsing, Execution and Caching</h3></div></div></div><p style="width:90%">

</p></div><div class="section" title="Page Parsing, Execution and Caching"><div class="titlepage"><div><div><h3 class="title"><a name="idp5287224"></a>Page Parsing, Execution and Caching</h3></div></div></div><p style="width:90%">

When a Rivet page is requested, it is transformed into an

ordinary Tcl script by parsing the file for the <? ?>

processing instruction tags. Everything outside these tags

without having to reload it (and re-parse it) from the disk.

The number of scripts stored in memory is configurable. This

feature can significantly improve performance.

</p></div><div class="section" title="Debugging Rivet and Apache"><div class="titlepage"><div><div><h3 class="title"><a name="idp9657152"></a>Debugging Rivet and Apache</h3></div></div></div><p style="width:90%">

</p></div><div class="section" title="Debugging Rivet and Apache"><div class="titlepage"><div><div><h3 class="title"><a name="idp5316320"></a>Debugging Rivet and Apache</h3></div></div></div><p style="width:90%">

If you are interested in hacking on Rivet, you're welcome to

contribute! Invariably, when working with code, things go

wrong, and it's necessary to do some debugging. In a server

Older »