Top
WebObjects Viewed Through Its Classes
As you learned at the end of the first chapter, WebObjects applications respond to HTTP requests and return responses in the form of dynamically generated HTML pages. The main loop of a WebObjects application, in which the application performs this work, is called the request-response loop. You have a very broad understanding of how this works: the web browser sends a request to the HTTP server, which forwards it to the WebObjects adaptor, which translates it into a form that a WebObjects application can understand. For the response, the process is reversed.
- The Classes in the Request-Response Loop
- Server and Application Level
- Session Level
- Request Level
- Page Level
- Database Integration Level
- How WebObjects Works-A Class Perspective
- Starting the Request-Response Loop
- Determining the Request Type
- Handling Component Action Requests
- Accessing the Session
- Creating or Restoring the Request Page
- Taking Input Values From a Request
- Invoking an Action
- Generating the Response
- Request Post-Processing
- Handling Direct Action Requests
- Invoking the Action
- Generating the Response
- Request Post-Processing
- Component Actions vs. Direct Actions
- Component Templates
- Associations and the Current Component
- Subcomponents and Component References