Table of Contents

Previous Section

State Storage Strategies

WebObjects gives you the option of storing state in various ways:

In the server. State is maintained in memory within a WebObjects application.
In the page. State is embedded in the HTML page that's returned to the user.
In cookies. State is embedded in name-value pairs ("cookies") in the HTTP header and passed between the client and server. Like "state-in-the-page," cookies store state on the client.
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 the next sections, "Comparison of Storage Options" and "A Closer Look at Storage Strategies." If you decide to use one of the other state-storage solutions, 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".

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