Table of Contents Previous Section

Storing State for Custom Objects

When state is stored in the server, the objects that hold state are kept intact in memory between transactions. In contrast, when state is stored in the page, in cookies, or in the filesystem, objects are asked to archive themselves before being put into storage. The objects that are part of the WebObjects and Foundation frameworks know how to archive themselves, so require no effort on your part. But if your application has custom classes that need to store state, these classes must know how to archive and unarchive themselves. How you implement archiving for custom classes depends on whether your application makes use of the Enterprise Objects framework and its EOEditingContext class.

Table of Contents Next Section