Top
Most applications must be able to preserve some application state between a user's requests. For example, if you're writing a catalog application, you must keep track of the items that the user has selected before the user actually fills out the purchasing information. By default, WebObjects stores application state on the server. If this doesn't meet your needs, WebObjects provides several alternatives strategies for storing state.
- Why Do You Need to Store State
- When Do You Need to Store State
- The Application Object and Application State
- The Session Object and Session State
- Component Objects and Component State
- A Closer Look at Storage Strategies
- State in the Server
- Using Cookies
- Storing State for Custom Objects
- Archiving Custom Objects in a Database Application
- Archiving Custom Objects in Other Applications
- Setting Session Time-Out
- Using awake and sleep
- Managing Component Resources
- Adjusting the Page Cache Size
- Using awake and sleep
- Client-Side Page Caching
- Page Refresh and WODisplayGroup