This chapter presents focused discussions of topics related to requests. The organization of the chapter loosely follows the typical order in which the servlet container and a servlet process the request. The chapter describes each task in isolation. See Chapter 9, "Creating Servlets," for an example of a complete servlet.
A request arrives at the servlet through the process discussed in Section 7.2. The servlet may inspect the headers of the request (Section 7.3). The servlet then interprets the content of the request, which is often contained in either parameters from an HTML form (Section 7.4) or in a SOAP message. Servlets that rely on maintaining state between requests most often let the servlet container manage state using sessions (Section 7.5). Servlets can also store state on the client using cookies (Section 7.6).
This chapter follows the conventions that request is a rwsf::HttpServletRequest object, that response is a rwsf::HttpServletResponse object and that any standalone lines of code occur within a servlet function such as doPost().
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo are registered trademarks of Rogue Wave Software, and HydraExpress is a trademark of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.