Documentation Archive Developer

Search

PATH Documentation > WebObjects 4.5 > WebObjects Developer's Guide

Table of Contents

Previous Section

State Storage Strategies

WebObjects gives you the option of storing state in a couple of different ways:

In the server. State is maintained in memory within a WebObjects application.
In custom stores. State is stored using a mechanism of your own design.

By default, WebObjects uses the first approach, storing state on the server. To determine whether you should use this default approach or try one of the other state-storage solutions, read "A Closer Look at Storage Strategies." If you decide to use another state-storage solution, you may have to set up custom objects so that they can be archived. To learn more about this issue, read "Storing State for Custom Objects".

An additional option when storing the state on the server is to utilize cookies for persistently storing the client's sessionID and instanceID. This allows the client to transparently have their session restored if they leave the application and return before their session has timed out. Methods on WOSession allow for the customization of this feature. This feature will be explained in more detail below.

You may find you need to control the amount of state that is stored. The sections "Controlling Session State" and "Controlling Component State" tell you how to do so.

Table of Contents Next Section