Main Menu
Lecture 1
Lecture 3
Lecture 4
Lecture 5
Lecture 6
Lecture 7
 

 

 

WOSession

WOApplication represents one instance of the application

One application instance for each running executable (e.g. one executable per machine with own application state)

Application.java is automatically created as a subclass of WOApplication, when you make a new project.

Each application instance has many sessions (manages multiple session objects)

A session is a user's view of your application

Log in, browse, submit data, Log Out.

Place to store state for your session

Session.java is automatically created as a sub Class of WOSession

Security

Each session has an automatically generated unique session ID - created when the user enters your site

Appears as garbage inside the URL - for security, so that no one else can look at your session

ID could be hidded in a cookie (but no need to)

Cookie is another way of securely remembering state

Server sends you a bit of information (a cookie)

When you get it, your Browser automatically sends a cookie back

Contains your name and state of where you are up to

WebObjects URLs

Top level application URL - deployed

http://www.host.com/cgi-bin/WebObjects/App

Session specific URL

.../WebObjects/App.woa/wo/gobblygook/1.7

.../Its a WebObjects App/ wo application name / its a component action not a dircect action / session ID / element id

Direct Connect URL - development

http://localhost:1223/cgi-bin/WebObjects/tut2