From 6b2d3262a3d09394e1c5777ef00898527d671f89 Mon Sep 17 00:00:00 2001 From: markt Date: Mon, 15 Sep 2008 00:02:11 +0000 Subject: [PATCH] Fix broken links reported on users list. git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@695311 13f79535-47bb-0310-9956-ffa450edef68 --- webapps/docs/architecture/overview.xml | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/webapps/docs/architecture/overview.xml b/webapps/docs/architecture/overview.xml index 5e93853c1..9fc9e19a3 100644 --- a/webapps/docs/architecture/overview.xml +++ b/webapps/docs/architecture/overview.xml @@ -43,8 +43,8 @@ This page provides an overview of the Tomcat server architecture. In the Tomcat world, a Server represents the whole container. Tomcat provides a default implementation of the -Server interface., -and this is rarely customized by users. +Server interface +which is rarely customized by users.

@@ -54,7 +54,7 @@ A Service is an intermediate component 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: -Service interface. +Service interface.

@@ -65,7 +65,7 @@ An 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 Engine interface +The Engine interface may be implemented to supply custom Engines, though this is uncommon.

@@ -80,9 +80,9 @@ A Host is an association of a network name, 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 -Hosts +Hosts because the -StandardHost +StandardHost implementation provides significant additional functionality.

@@ -90,14 +90,13 @@ implementation provides significant additional functionality.

A Connector handles communications with the client. There are multiple -connectors available with Tomcat, all of which implement the -Connector -interface. These include the -Coyote connector which is used for +connectors available with Tomcat. These include the +HTTP connector which is used for most HTTP traffic, especially when running Tomcat as a standalone server, -and the JK2 connector which implements -the AJP procotol used when connecting Tomcat to an Apache HTTPD server. -Creating a customized connector is a significant effort. +and the AJP connector 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.

@@ -107,10 +106,10 @@ A Context represents a web application. A Host may contain multiple contexts, each with a unique path. The -Context +Context interface may be implemented to create custom Contexts, but this is rarely the case because the - + StandardContext provides significant additional functionality.

-- 2.11.0