You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by ma...@apache.org on 2008/09/15 02:02:11 UTC
svn commit: r695311 - /tomcat/trunk/webapps/docs/architecture/overview.xml
Author: markt
Date: Sun Sep 14 17:02:11 2008
New Revision: 695311
URL: http://svn.apache.org/viewvc?rev=695311&view=rev
Log:
Fix broken links reported on users list.
Modified:
tomcat/trunk/webapps/docs/architecture/overview.xml
Modified: tomcat/trunk/webapps/docs/architecture/overview.xml
URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/architecture/overview.xml?rev=695311&r1=695310&r2=695311&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/architecture/overview.xml (original)
+++ tomcat/trunk/webapps/docs/architecture/overview.xml Sun Sep 14 17:02:11 2008
@@ -43,8 +43,8 @@
In the Tomcat world, a
<a href="../config/server.html">Server</a> represents the whole container.
Tomcat provides a default implementation of the
-<a href="../catalina/docs/api/org/apache/catalina/Server.html">Server interface.</a>,
-and this is rarely customized by users.
+<a href="../api/org/apache/catalina/Server.html">Server interface</a>
+which is rarely customized by users.
</p>
</subsection>
@@ -54,7 +54,7 @@
which lives inside a Server and ties one or more Connectors to exactly one
Engine. The Service element is rarely customized by users, as the default
implementation is simple and sufficient:
-<a href="../catalina/docs/api/org/apache/catalina/Service.html">Service interface</a>.
+<a href="../api/org/apache/catalina/Service.html">Service interface</a>.
</p>
</subsection>
@@ -65,7 +65,7 @@
pipeline for a specific Service. As a Service may have multiple Connectors,
the Engine received and processes all requests from these connectors, handing
the response back to the appropriate connector for transmission to the client.
-The <a href="../catalina/docs/api/org/apache/catalina/Engine.html">Engine interface</a>
+The <a href="../api/org/apache/catalina/Engine.html">Engine interface</a>
may be implemented to supply custom Engines, though this is uncommon.
</p>
<p>
@@ -80,9 +80,9 @@
e.g. www.yourcompany.com, to the Tomcat server. An Engine may contain
multiple hosts, and the Host element also supports network aliases such as
yourcompany.com and abc.yourcompany.com. Users rarely create custom
-<a href="../catalina/docs/api/org/apache/catalina/Host.html">Hosts</a>
+<a href="../api/org/apache/catalina/Host.html">Hosts</a>
because the
-<a href="../catalina/docs/api/org/apache/catalina/core/StandardHost.html">StandardHost
+<a href="../api/org/apache/catalina/core/StandardHost.html">StandardHost
implementation</a> provides significant additional functionality.
</p>
</subsection>
@@ -90,14 +90,13 @@
<subsection name="Connector">
<p>
A Connector handles communications with the client. There are multiple
-connectors available with Tomcat, all of which implement the
-<a href="../catalina/docs/api/org/apache/catalina/Connector.html">Connector
-interface.</a> These include the
-<a href="../config/coyote.html">Coyote connector</a> which is used for
+connectors available with Tomcat. These include the
+<a href="../config/http.html">HTTP connector</a> which is used for
most HTTP traffic, especially when running Tomcat as a standalone server,
-and the <a href="../config/jk2.html">JK2 connector</a> which implements
-the AJP procotol used when connecting Tomcat to an Apache HTTPD server.
-Creating a customized connector is a significant effort.
+and the <a href="../config/ajp.html">AJP connector</a> which implements
+the AJP procotol used when connecting Tomcat to a web server such as
+Apache HTTPD server. Creating a customized connector is a significant
+effort.
</p>
</subsection>
@@ -107,10 +106,10 @@
<a href="../config/context.html">Context</a>
represents a web application. A Host may contain multiple
contexts, each with a unique path. The
-<a href="../catalina/docs/api/org/apache/catalina/Context.html">Context
+<a href="../api/org/apache/catalina/Context.html">Context
interface</a> may be implemented to create custom Contexts, but
this is rarely the case because the
-<a href="../catalina/docs/api/org/apache/catalina/core/StandardContext.html">
+<a href="../api/org/apache/catalina/core/StandardContext.html">
StandardContext</a> provides significant additional functionality.
</p>
</subsection>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org