Chapter 10: HTTP Connectors The following areas are
Chapter 10: HTTP Connectors The following areas are covered in this chapter: . Using Tomcat 6 default Java HTTP/1.1 Connector . Using Tomcat 6 Java NIO (Advanced IO) HTTP/1.1 Connector . Using Tomcat 6 native APR (native code) HTTP/1.1 Connector . Blocking and non-blocking operations . Supporting Comet . Running Tomcat behind a proxy server . Setting up SSL . Performance tuning HTTP Connectors The standard HTTP Connectors included with Tomcat 6 provide the ability to run Tomcat in a standalone mode. In this mode, Tomcat can respond to HTTP requests directly from users browsers without the assistance of a separate Web server. In addition to requests for servlets and JSPs, the HTTP connectors also respond to requests for static contents, such as static Web pages and images. The HTTP Connectors are Java classes that implement the HTTP protocol. An HTTP connector is invoked when there is an HTTP request on the Connector port. The port that the Connector listens on is specified in the $CATALINA_HOME/conf/server.xmlconfiguration file, and is set to 8080 by default. The Connector class has code to parse the HTTP request and take the required action of either serving up static content or passing the request through the Tomcat Servlet Engine. The HTTP Connector implements the HTTP/1.1 protocol, and all protocol features. For clients that support only HTTP/1.0, the Connector degrades gracefully to support the legacy protocol. There are multiple HTTP Connector implementations available with Tomcat 6. These include: . Java-based HTTP/1.1 (Coyote) Connector . Java-based High Performance NIO HTTP Connector . Native code optimized APR HTTP Connector The Java-based Coyote Connector is the most mature of the three variations, it is extremely stable, works well, has great performance, and should be the choice for most situations especially if you are just beginning to use Tomcat 6. The high-performance NIO HTTP connector provides non-blocking IO and Comet support, if you are using a software library that requires (or benefits from) this additional support, you may want to use this connector instead. Be aware, however, even as late as Java SE 5, there are serious bugs in the Java NIO library that may affect stability of your Tomcat server. On highly loaded systems, the optimization possibilities offered by the APR HTTP Connector can be very attractive. This is the newest of the three connector implementations, but potentially offers the highest level of performance improvement by leveraging proven operating system level optimization on
For high quality website hosting services please check cheap web hosting website.