notify-dpml AT lists.ibiblio.org
Subject: DPML Notify
List archive
svn commit: r1416 - in development/main/central/site/src/docs/products/transit: concepts properties
- From: mcconnell AT netcompartner.com
- To: notify-dpml AT lists.ibiblio.org
- Subject: svn commit: r1416 - in development/main/central/site/src/docs/products/transit: concepts properties
- Date: Sun, 09 Jan 2005 15:38:26 +0100
Author: mcconnell
Date: Sun Jan 9 15:38:26 2005
New Revision: 1416
Modified:
development/main/central/site/src/docs/products/transit/concepts/hosts.xml
development/main/central/site/src/docs/products/transit/properties/cache.xml
development/main/central/site/src/docs/products/transit/properties/hosts.xml
Log:
add descriptuion of the role of transit hosts and links to related properties
and guide material
Modified:
development/main/central/site/src/docs/products/transit/concepts/hosts.xml
==============================================================================
---
development/main/central/site/src/docs/products/transit/concepts/hosts.xml
(original)
+++
development/main/central/site/src/docs/products/transit/concepts/hosts.xml
Sun Jan 9 15:38:26 2005
@@ -8,11 +8,34 @@
</properties>
<body>
+
<section name="Host Management">
<p>
+ Transit uses <a href="artifact.html">artifact uris</a> to identify
+ a resource. These identifiers are in turn mapped internally to a
+ a repository url (i.e. mapping identity to a location). Locations
+ are defined relative to one or more a Transit host.
+ </p>
+
+ <p>
+ Each Transit host declares a base url, an implementation strategy
+ (typically dealing with uri to url mapping), and policies concerning
+ the handling of timestamped resources.
</p>
+ <p>
+ The Transit <a href="../properties/hosts.html">hosts configuration</a>
+ enables the declaration of local file based repositories and remote
+ repositories accessible via http and https protocols.
+ </p>
+
+ <p>
+ Example of artifact retrival and remote repositories are included in
+ the <a href="/guide/transit/resources/index.html">Transit Guide</a>.
+ </p>
+
</section>
+
</body>
</document>
Modified:
development/main/central/site/src/docs/products/transit/properties/cache.xml
==============================================================================
---
development/main/central/site/src/docs/products/transit/properties/cache.xml
(original)
+++
development/main/central/site/src/docs/products/transit/properties/cache.xml
Sun Jan 9 15:38:26 2005
@@ -28,23 +28,17 @@
<body>
<section name="Cache Properties">
<p>
- The <a href="../../../concepts/index.html#local_cache_manager">local
cache manager</a>
- stores the downloaded
- <a href="../../../concepts/index.html#artifact">artifact</a>s on
your
- local file system.
- This allows your DPML-enabled applications to quickly retrieve
- required resources.
+ The transit system stores the downloaded resources
+ on your local file system. The cache provides DPML-enabled
+ applications with quickly retrieval of required resources.
</p>
<p>
- When requested by your application, the cache manager will first
+ When requested by your application, a cache manager will first
check the local cache for the required resource.
If the resource is not available in the local cache, the cache
manager
- will then query each
- <a href="../../../concepts/index.html#remote_repository">remote
repository</a>
- defined as a
- <a href="../../../concepts/index.html#host">host</a>
- until the resource is found.
+ will then query each remote repository defined under the <a
href="hosts.html">
+ host configuration</a> until the resource is resolved.
</p>
<p>
@@ -63,12 +57,12 @@
</tr>
<tr>
<td>dpml.transit.cache.location</td>
- <td><a
href="../../../concepts/index.html#dpml_home">${dpml.home}</a>/main</td>
+ <td><code>${dpml.home}/cache</code></td>
<td>The location of the cache system.</td>
</tr>
<tr>
<td>dpml.transit.cache.class</td>
- <td><a
href="../../../../@TRANSIT-DOCS-PATH@/net/dpml/transit/artifact/FieldCacheHandler.html">net.dpml.transit.artifact.FileCacheHandler</a></td>
+ <td>net.dpml.transit.artifact.FileCacheHandler</td>
<td>
The class that implements the cache handler interface
<a
href="../../../../@TRANSIT-DOCS-PATH@/net/dpml/transit/artifact/CacheHandler.html">net.dpml.transit.artifact.CacheHandler</a>.
Modified:
development/main/central/site/src/docs/products/transit/properties/hosts.xml
==============================================================================
---
development/main/central/site/src/docs/products/transit/properties/hosts.xml
(original)
+++
development/main/central/site/src/docs/products/transit/properties/hosts.xml
Sun Jan 9 15:38:26 2005
@@ -30,7 +30,8 @@
A Resource Host is a place where Artifacts can be downloaded. Transit
is capable of handling many types of resource hosts. Conceptually,
you
only need to implement the
- <code>net.dpml.transit.artifact.ResourceHost</code> interface, and
+ <code><a
href="../../../../@TRANSIT-DOCS-PATH@/net/dpml/transit/artifact/ResourceHost.html">
+ net.dpml.transit.artifact.ResourceHost</a></code> interface, and
specify the implementation class of the host handler.
host.
</p>
@@ -126,9 +127,10 @@
</tr>
<tr>
<td>dpml.transit.resourcehost.class</td>
- <td>net.dpml.transit.artifact.ClassicResourceHost</td>
+ <td>(see description)</td>
<td>
Defines the class to use for the management of the remote host.
+ If undefined the value defaults to
<code>net.dpml.transit.artifact.ClassicResourceHost</code>.
</td>
</tr>
<tr>
- svn commit: r1416 - in development/main/central/site/src/docs/products/transit: concepts properties, mcconnell, 01/09/2005
Archive powered by MHonArc 2.6.24.