Home

This Chapter
-Chapter 20: Early HttpSession Invalidation
-HttpSession Invalidation in Struts
-Early HttpSession Invalidation
-Summary

Table of Contents
-Introduction
-Chapter 1: Model 2 and Struts
-Chapter 2: Input Validation with Action Forms
-Chapter 3: The HTML Tag Library
-Chapter 4: Input Validation and Data Conversion
-Chapter 5: The Validator Plugin
-Chapter 6: The Expression Language
-Chapter 7: JSTL
-Chapter 8: The Bean Tag Library
-Chapter 9: The Logic Tag Library
-Chapter 10: Struts-EL, Nested, selectLabel
-Chapter 11: Message Handling and Internationalization
-Chapter 12: The Tiles Framework
-Chapter 13: Securing Struts Applications
-Chapter 14: The Config Object
-Chapter 15: The Persistence Layer
-Chapter 16: Object Caching
-Chapter 17: File Upload and File Download
-Chapter 18: Paging and Sorting
-Chapter 19: Preventing Double Submits
-Chapter 20: Early HttpSession Invalidation
-Chapter 21: Decorating Request Objects
-Chapter 22: How Struts Works

Previous
Next

 

Chapter 20

Early HttpSession Invalidation

HttpSession objects are useful, however they also consume memory. Therefore, when an HttpSession object is no longer needed, it should be destroyed by calling its invalidate method. Many programmers provide a link for users to log out, but few use it. Often, they simply close the browse when they are done with an application. Waiting for HttpSession objects to die naturally will cause more memory to be used longer that it needs be. This chapter discusses a technique that forces HttpSession invalidation when the browser is closed.

Previous
Next