svn commit: r786720 - in /websites/staging/trafficserver/trunk/content/docs/trunk/sdk: http-headers/guide-to-trafficserver-http-header-system/ mutex-guide/ remap-plugin/

[bu...@apache.org]

Author: buildbot
Date: Wed Mar  9 02:24:01 2011
New Revision: 786720

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/sdk/remap-plugin/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.html Wed Mar  9 02:24:01 2011
@@ -45,11 +45,11 @@ or HTTP header.</p>
 it belongs - this is called the field's <strong>parent header</strong>. The <code>TSMimeField*</code> 
 functions in older versions of the SDK have been deprecated, as they do not 
 require the parent header as inputs. The current version of Traffic Server 
-uses new functions, the <code>**TSMimeHdrField***</code> series, which require you to 
+uses new functions, the <strong><code>TSMimeHdrField</code></strong> series, which require you to 
 specify the location of the parent header along with the location of the MIME 
-field. For every deprecated <code>TSMimeField*</code> function, there is a new, preferred 
-<code>TSMimeHdrField*</code> function. Therefore, you should use the <code>**TSMimeHdrField***</code> 
-functions instead of the deprecated <code>TSMimeField*</code> series. Examples are provided 
+field. For every deprecated <em><code>TSMimeField</code></em> function, there is a new, preferred 
+<code>TSMimeHdrField*</code> function. Therefore, you should use the <strong><code>TSMimeHdrField</code></strong> 
+functions instead of the deprecated <em><code>TSMimeField</code></em> series. Examples are provided 
 below.</p>
 <p>Instead of:</p>
 <div class="codehilite"><pre><span class="n">TSMLoc</span> <span class="n">TSMimeFieldCreate</span> <span class="p">(</span><span class="n">TSMBuffer</span> <span class="n">bufp</span><span class="p">)</span>

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/mutex-guide/index.en.html Wed Mar  9 02:24:01 2011
@@ -63,7 +63,7 @@ to protect data from simultaneous access
 as a lock that protects data in one program thread from being accessed by another 
 thread.</p>
 <p>The Traffic Server API provides two functions that attempt to access and lock 
-the data: <code>InkMutexLockTry</code> and <code>TSMutexLock</code>. <code>**TSMutexLock**</code> is a blocking 
+the data: <code>InkMutexLockTry</code> and <code>TSMutexLock</code>. <strong><code>TSMutexLock</code></strong> is a blocking 
 call - if you use it, you can slow Traffic Server performance because transaction 
 processing pauses until the mutex is unlocked. It should be used only on threads 
 created by the plugin <code>TSContThreadCreate</code>. Never use it on a continuation 

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/sdk/remap-plugin/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/sdk/remap-plugin/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/sdk/remap-plugin/index.en.html Wed Mar  9 02:24:01 2011
@@ -67,16 +67,16 @@ the header file location is: <code>/usr/
 <p>A remap plugin is required to implement the following functions:</p>
 <ul>
 <li>
-<p><a href="ch03s02.html#tsremap_init"><code><strong>tsremap_init</strong></code></a>: the remap initialization
+<p><a href="/link/to/doxygen"><strong><code>tsremap_init</code></strong></a>: the remap initialization
 function, called once when the plugin is loaded</p>
 </li>
 <li>
-<p><a href="ch03s02.html#tsremap_new_instance"><code><strong>tsremap_new_instance</strong></code></a>: a new
+<p><a href="/link/to/doxygen"><strong><code>tsremap_new_instance</code></strong></a>: a new
 instance is created for each rule associated with the plugin. Called each time
 the plugin used in a remap rule (this function is what processes the pparam values)</p>
 </li>
 <li>
-<p><a href="ch03s02.html#tsremap_remap"><code><strong>tsremap_remap</strong></code></a>: the entry point used by
+<p><a href="/link/to/doxygen"><strong><code>tsremap_remap</code></strong></a>: the entry point used by
 Traffic Server to find the new URL to which it remaps; called every time a request comes in</p>
 </li>
 </ul>