
How WebObjects Works—A Class Perspective
75
Figure 20. URL to Start a WebObjects Application
This URL does not contain a session ID, so the application object creates a
new session by performing the following steps:
1. It sends itself a
createSession message.
2. As part of the
createSession method, it sends the init message or the
constructor message to the WOSession (or WebSession) class to create
a new session object.
3. It sends the
awake message to the session object.
If the request is part of an existing session, the request URL looks like the
one shown in Figure 21.
Figure 21. WebObjects URL in an Existing Session
This URL contains all of the information necessary to restore the state of
the existing session. The session ID comes right after the application name
in the URL. Because sessions are designed to protect the data of one user’s
http://ursa/cgi-bin/WebObjects/SomeWebApp
name of the Web server's
cgi-bin directory
HTTP
server name
adaptor
name
application path relative to
<
DocRoot
>/ WebObjects
http://ursa/cgi-bin/WebObjects/SomeWebApp.woa/19335471518261838039837077512/Main.wo/62793212911/0.1.0/-/ursa
HTTP
server
name
adaptor
name
application
name
secure
session
ID
page
name
context
ID
application
instance
number
active
element
ID
application
server
name
Commentaires sur ces manuels