• Table of Contents
• Previous Next

PATH  WebObjects 4.0 Documentation > What's New in WebObjects 4.0

Table of Contents Previous Section

Direct Actions

Previously, all WebObjects applications used the same request-handling scheme: the request to perform an action is passed from the application to the session to the request component. The request component is the component that generated the response for the previous request. Thus, the component that generates the response for one request must be preserved so that it can perform the next requested action. Because components had to be preserved across cycles of the request-response loop, all applications were required to keep some session state.

In WebObjects 4.0, you can set up all or part of your application to handle direct actions. With direct actions, the action is sent directly to an object that can handle it. Direct actions have several advantages over component actions:

• Direct actions have simpler, static URLs. Your users can bookmark a direct action URL and return to it at any time.

• Direct actions have simpler request handling.

• By default, direct actions don't use session objects and thus don't store state. If you are writing a stateless application, you may find it easier to frame your application logic using direct actions instead of component actions.

Table of Contents Next Section

Legacy Legacy Mac OS X Reference Library WebObjects 4.0 Developer Documentation