This patch enhances the wording in a few places, corrects a few spelling and grammatical issues, etc. - a minor overhaul of J-F's major overhaul of my minor document :-)
Ian
--- webapps/tomcat-docs/config/connectors.xml.orig Sun Jun 23 14:03:13 2002 +++ webapps/tomcat-docs/config/connectors.xml Sun Jun 23 14:08:52 2002 @@ -17,8 +17,9 @@ <section name="Introduction"> <p> -JTC means Jakarta-Tomcat-Connectors. jakarta-tomcat-connectors is the -repository of the Tomcat connectors sources. +JTC stands for Jakarta-Tomcat-Connectors. The name comes from +jakarta-tomcat-connectors, the +CVS repository of the Tomcat connectors sources. The connectors are released together with Tomcat. For example you can find the connectors sources in http://jakarta.apache.org/builds/jakarta-tomcat-4.x/release/v4.x.y/src/ @@ -26,17 +27,18 @@ jakarta-tomcat-connectors-4.x.y-src.tar.gz </p> <p> -There are two different types of connectors. Connectors that allow browsers to -connect directly to the Tomcat and connectors that do it through a Web Server. +There are two different types of connectors; connectors that allow browsers to +connect directly to the Tomcat and those connect from a Web Server. </p> <p> -The connectors allowing direct connections are in the binary of Tomcat. +The connectors allowing direct connections are included in the binary of Tomcat. They are jar files. </p> <p> -The connectors used with a Web Server are made of 2 components. One written -in Java and the other written in C. The Java part is made of jar files are -inclosed in the Tomcat binaries. +The connectors used with a Web Server are made of 2 components, one written +in Java and the other written in C. The Java part is made of jar files that are +enclosed in the Tomcat binaries. The C part normally needs to be built using +some native-dependant compilation (e.g., apxs for Apache, Visual C++ for IIS). </p> <p> The binary builds of connectors are available in @@ -79,7 +81,7 @@ <tr> <td>mod_jserv</td><td>ajp1.2</td> <td>Ajp11</td> - <td>Obsolete Read more at + <td>Obsolete. Read more at <a href="http://java.apache.org/jserv/index.html";> JServ</a></td> </tr> @@ -94,7 +96,7 @@ <tr> <td>mod_jk2</td><td>ajp1.3/ajp1.4</td> <td>CoyoteConnector+JkCoyoteHandler</td> - <td>Current developpements. Enabled by default in 4.1; works in 4.0. + <td>Current development. Enabled by default in 4.1; works in 4.0. mod_jk2 supports in-process JVM and load balancing. See <a href="jk2.html">Coyote JK 2</a> </td> @@ -113,12 +115,13 @@ </section> <section name="Why a Tomcat connector with a native Web Server?"> <p> -A Web Server can host different applications written using PERL, PHP, C or -other language. If one application is written in Java using the Servlet -API a connector is need to route the requests from the Web Server to the -Servlet Engine. In the case a Web Server specific connector is needed. -Most of the Web Servers allow to load dynamic extentions (DLL). Some of these -extentions are available in the binary builds of connectors. +A native Web Server (such as Apache httpd or Microsoft IIS) can host +multiple applications written using PERL, PHP, C or +other languages on a given platform. If an application is written in Java using the Servlet +API, a connector is needed to route the requests from the Web Server to the +Servlet Engine. In this case a Web Server-specific connector is needed. +Most of the Web Servers allow loading dynamic extentions (DLL). Some of these +extensions are available in the binary builds of connectors. </p> </section>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
