Table of Contents
Previous Section
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 in the server. Before examining how to use these different strategies, let's take a look at some of their advantages and disadvantages.
Table of Contents
Next Section