svn commit: r780510 - in /websites/staging/trafficserver/trunk/content/docs/trunk/sdk: getting-started/index.en.html how-to-create-trafficserver-plugins/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Mon Dec 13 00:39:07 2010
New Revision: 780510

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/getting-started/index.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/getting-started/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/getting-started/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/getting-started/index.en.html Mon Dec 13 00:39:07 2010
@@ -61,14 +61,14 @@ Server loads when it is started. Your pl
 are registered for specific Traffic Server events. When Traffic Server needs
 to process an event, it invokes any and all call-back functions you've registered
 for that event type.</p>
-<p><img alt="[Caution]" src="images/docbook/caution.png" />
+<p><img alt="[Caution]" src="/images/docbook/caution.png" />
 <strong>Caution</strong></p>
 <p>Since plugins add object code to Traffic Server, programming errors in a plugin
 can have serious implications. Bugs in your plugin, such as an out-of-range
 pointer, can cause Traffic Server processes to crash and may ultimately result
 in unpredictable behavior.</p>
 <h4 id="PluginProcess">Plugin Process</h4>
-<p>![Plugin Process][images/plugin_process.jpg]</p>
+<p><img alt="Plugin Process" src="/images/sdk/plugin_process.jpg" /></p>
 <h3 id="possible_uses_for_plugins">Possible Uses for Plugins</h3>
 <p>Possible uses for plugins include the following:</p>
 <ul>
@@ -114,7 +114,7 @@ port and then uses Traffic Server's prox
 <p>The figure below, <a href="#possibleTSplugins">Possible Traffic Server Plugins</a>,
 illustrates several types of plugins.</p>
 <h4 id="possibleTSplugins">Possible Traffic Server Plugins</h4>
-<p>![Possible Traffic Server Plugins][images/Uses.jpg]</p>
+<p><img alt="Possible Traffic Server Plugins" src="/images/sdk/Uses.jpg" /></p>
 <p>You can find basic examples for many plugins in the SDK sample code:</p>
 <ul>
 <li>
@@ -145,7 +145,7 @@ The <code>plugin.config</code> file also
 plugin's initialization function, <code>TSPluginInit</code>. The <code>records.config</code> file 
 defines the path to each plugin shared library, as described in <a href="SpecifyingPluginLocation.html">Specify the 
 Plugin's Location</a>.</p>
-<p>![[Note]][images/docbook/note.png]
+<p><img alt="[Note]" src="/images/docbook/note.png" />
 <strong>Note</strong></p>
 <p>The path for each of these files is <em><code><root_dir></code></em><code>/config/</code>, where <em><code><root_dir></code></em>
 is where you installed Traffic Server.</p>

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.html Mon Dec 13 00:39:07 2010
@@ -95,12 +95,12 @@ An executing thread calls back a continu
 a continuation receives an event, it wakes up, does some work, and either destroys
 itself or goes back to sleep &amp; waits for the next event.</p>
 <h4 id="traffic_server_internals__tsinternals">Traffic Server Internals #### {TSInternals}</h4>
-<p><img alt="Traffic Server Internals" src="images/event_sys80.jpg" /></p>
+<p><img alt="Traffic Server Internals" src="/images/sdk/event_sys80.jpg" /></p>
 <p>Plugins are typically implemented as continuations. All of the sample code
 plugins (except <code>hello-world</code>) are continuations that are created when Traffic
 Server starts up; they then wait for events that trigger them into activity.</p>
 <h4 id="traffic_server_with_plugins__tswithplugins">Traffic Server with Plugins #### {TSwithPlugins}</h4>
-<p><img alt="Traffic Server with Plugins" src="images/evt_plugin120.jpg" /></p>
+<p><img alt="Traffic Server with Plugins" src="/images/sdk/evt_plugin120.jpg" /></p>
 <p>A plugin may consist of just one static continuation that is called whenever
 certain events happen. Examples of such plugins include <code>blacklist-1.c</code>, <code>basic-auth.c</code>,
 and <code>redirect-1.c</code>. Alternatively, a plugin might dynamically create other
@@ -141,7 +141,7 @@ cache or Traffic Server might fetch it f
 diagram shows some states in a typical transaction - specifically, the scenario
 wherein content is served from cache.</p>
 <h4 id="SimplifiedHTTPTransaction">Simplified HTTP Transaction</h4>
-<p><img alt="Simplified HTTP Transaction" src="images/transact75.jpg" /></p>
+<p><img alt="Simplified HTTP Transaction" src="/images/sdk/transact75.jpg" /></p>
 <p>In the diagram above, Traffic Server accepts the client connection, reads the
 request headers, looks up the origin server's IP address, and looks for the
 requested content in the cache. If the content is not in the cache (a "miss"),
@@ -158,7 +158,7 @@ and sends a reply. If the reply is an er
 the reply is not an error, then Traffic Server first sends the response content
 before it closes the transaction.</p>
 <h4 id="APIHooksCorrespondingtoStates">API Hooks Corresponding to States</h4>
-<p><img alt="API Hooks Corresponding to States Listed in" src="images/transact_hook75.jpg" /></p>
+<p><img alt="API Hooks Corresponding to States Listed in" src="/images/sdk/transact_hook75.jpg" /></p>
 <p>You use hooks as triggers to start your plugin. The name of a hook reflects
 the Traffic Server state that was <em>just completed</em>. For example, the "OS DNS
 lookup" hook wakes up a plugin right <em>after</em> the origin server DNS lookup.
@@ -167,7 +167,7 @@ hook is the right one to use. The Blackl
 shown in the <a href="#BlacklistPlugin">Blacklist Plugin</a>
 diagram below.</p>
 <h4 id="BlacklistPlugin">Blacklist Plugin</h4>
-<p><img alt="Blacklist Plugin" src="/images/blacklist75.jpg" /></p>
+<p><img alt="Blacklist Plugin" src="/images/sdk/blacklist75.jpg" /></p>
 <p>Traffic Server calls the Blacklist plugin right after the origin server DNS
 lookup. The plugin checks the requested host against a list of blacklisted
 servers; if the request is allowed, then the transaction proceeds. If the host