WebObjects tracking data

Embedded in URL

.../WebObjects/App.woa/wo/sessionID/contextID.elementID

Each session has a unique ID

Each request/response transaction has a unique context

The target component instance is part of the context

The elementID is the dynamic element that triggered the action

Also, if multiple instances of application running, URL contains applicationID

Tracking in a cookie

put the sessionID in a cookie rather than in the URL

public Session() {
    super():
    //disable session id in URL
    setStoresIDsInURLs(false);
    //enable cookies
    setStoresIDsInCookies(true);
}

1. Maintenance of state is mainly a server side issue
2. Web browser - caches pages and cookies
3. Application - only some things like hit count
4. Session - Most state kept in sessin object - used mostly to keep track of user
5. Database - for long-term persistance
   

Page updated August 26, 2004