Book Image

Tomcat 6 Developer's Guide

Book Image

Tomcat 6 Developer's Guide

Overview of this book

While Tomcat is one of the most popular servlet containers, its inner workings still remain a mystery to many developers. If you only have a superficial familiarity of how this container actually functions, much of its power remains untapped and underutilized. This book will provide you with all that you need to undertand how to effectively use Apache Tomcat. This book begins by providing detailed instructions on building a Tomcat distribution. The next few chapters introduce you to the conceptual underpinnings of web servers, the Java EE and servlet specifications, and the Tomcat container. Subsequent chapters address the key Tomcat components, taking care to provide you with the information needed to understand the internal workings of each component. Detailed examples let you walk through a Tomcat installation, stepping into key Tomcat components, as well as into your own custom servlets. During the course of the book you will encounter various structural components such as the Server and Service; containers such as the Engine, Host, Context, and Wrapper; and helpers such as the Loader, Manager, and Valve. You will also see how Tomcat implements the JNDI API to provide both a directory service for storage agnostic access to its resources, as well as a naming service that implements the Java EE Environment Naming Context. Along the way you will learn how various elements of the servlet 2.5 specification, as well as the HTTP RFCs are implemented by a servlet container. By the end of your journey, you will be able to count yourself as part of the elite minority of Java EE web developers who truly understand what goes on under the covers of a servlet container.
Table of Contents (17 chapters)
Tomcat 6 Developer's Guide
Credits
About the author
Acknowledgement
About the reviewers
Preface

Chapter 11. The Manager Component

HTTP is intrinsically a stateless protocol. Each incoming request is a separate independent event, and once the server has responded to a given request, it does not hold any information about the requesting client.

This statelessness was well suited for the original intent of the Internet as a global file sharing mechanism, where a client may connect to a server and request a particular file. The client would then wait on that connection for the server to respond with the contents of the specified file. Once the file had been transferred, the connection would be closed and the server would retain no active memory of the client that it had just serviced.

This resulted in an architecture that was highly performant and scalable, as a server incurred minimal overhead while performing its core task of accessing and transmitting a file.

The challenge, however, is that any non-trivial web application does much more than just retrieve a file or resource. In applications...