trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1044977 - in /trafficserver/site/branches/ats-cms/content/docs/trunk/sdk: getting-started/index.en.mdtext how-to-create-trafficserver-plugins/index.en.mdtext
Date Mon, 13 Dec 2010 00:38:59 GMT
Author: igalic
Date: Mon Dec 13 00:38:59 2010
New Revision: 1044977

URL: http://svn.apache.org/viewvc?rev=1044977&view=rev
Log:
reverting to previos version for easier copying of the images from original site.

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext?rev=1044977&r1=1044976&r2=1044977&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext
Mon Dec 13 00:38:59 2010
@@ -66,7 +66,7 @@ are registered for specific Traffic Serv
 to process an event, it invokes any and all call-back functions you've registered
 for that event type.
 
-![[Caution]](images/docbook/caution.png)
+![[Caution]](/images/docbook/caution.png)
 **Caution**
 
 Since plugins add object code to Traffic Server, programming errors in a plugin
@@ -76,7 +76,7 @@ in unpredictable behavior.
 
 #### Plugin Process #### {#PluginProcess}
 
-![Plugin Process][images/plugin_process.jpg]
+![Plugin Process](/images/sdk/plugin_process.jpg)
 
 ### Possible Uses for Plugins
 
@@ -115,7 +115,7 @@ illustrates several types of plugins.
 
 #### Possible Traffic Server Plugins #### {#possibleTSplugins}
 
-![Possible Traffic Server Plugins][images/Uses.jpg]
+![Possible Traffic Server Plugins](/images/sdk/Uses.jpg)
 
 You can find basic examples for many plugins in the SDK sample code:
 
@@ -145,7 +145,7 @@ plugin's initialization function, `TSPlu
 defines the path to each plugin shared library, as described in [Specify the 
 Plugin's Location](SpecifyingPluginLocation.html).
 
-![[Note]][images/docbook/note.png]
+![[Note]](/images/docbook/note.png)
 **Note**
 
 The path for each of these files is _`<root_dir>`_`/config/`, where _`<root_dir>`_

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.mdtext?rev=1044977&r1=1044976&r2=1044977&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.mdtext
(original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/index.en.mdtext
Mon Dec 13 00:38:59 2010
@@ -75,7 +75,7 @@ itself or goes back to sleep & waits for
 
 #### Traffic Server Internals #### {TSInternals}
 
-![Traffic Server Internals](images/event_sys80.jpg)
+![Traffic Server Internals](/images/sdk/event_sys80.jpg)
 
 Plugins are typically implemented as continuations. All of the sample code
 plugins (except `hello-world`) are continuations that are created when Traffic
@@ -83,7 +83,7 @@ Server starts up; they then wait for eve
 
 #### Traffic Server with Plugins #### {TSwithPlugins}
 
-![Traffic Server with Plugins](images/evt_plugin120.jpg)
+![Traffic Server with Plugins](/images/sdk/evt_plugin120.jpg)
 
 A plugin may consist of just one static continuation that is called whenever
 certain events happen. Examples of such plugins include `blacklist-1.c`, `basic-auth.c`,
@@ -133,7 +133,7 @@ wherein content is served from cache.
 
 #### Simplified HTTP Transaction #### {#SimplifiedHTTPTransaction}
 
-![Simplified HTTP Transaction](images/transact75.jpg)
+![Simplified HTTP Transaction](/images/sdk/transact75.jpg)
 
 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
@@ -154,7 +154,7 @@ before it closes the transaction.
 
 #### API Hooks Corresponding to States #### {#APIHooksCorrespondingtoStates}
 
-![API Hooks Corresponding to States Listed in](images/transact_hook75.jpg)
+![API Hooks Corresponding to States Listed in](/images/sdk/transact_hook75.jpg)
 
 You use hooks as triggers to start your plugin. The name of a hook reflects
 the Traffic Server state that was _just completed_. For example, the "OS DNS
@@ -166,7 +166,7 @@ diagram below.
 
 #### Blacklist Plugin #### {#BlacklistPlugin}
 
-![Blacklist Plugin](/images/blacklist75.jpg)
+![Blacklist Plugin](/images/sdk/blacklist75.jpg)
 
 Traffic Server calls the Blacklist plugin right after the origin server DNS
 lookup. The plugin checks the requested host against a list of blacklisted



Mime
View raw message