See Below
Guido Neitzer wrote:
On 05.04.2007, at 10:16, Fred Shurtleff wrote:
I checked the session (using Session session = (Session) session();)
immediately B4 setting the session user and again when I retrieved
the session user, and they were, in fact, DIFFERENT. So this explains
WHY the null user(and why the KVC calls seemingly did not work), but
opens up another issue - how are multiple sessions spawned? I do
understand the process of session ID creation and how requests are
matched with active, cached session ID's, but what I don't understand
is how my app has created >1 sessions when I am the only user running
direct under the localhost??
- Use of direct actions without properly restoring an existing session.
What is involved in 'restoring an existing session' - briefly?
My app uses Direct Actions - this is in Application.java -
// set direct actions as defualt
WORequestHandler directActionRequestHandler =
requestHandlerForKey("wa");
setDefaultRequestHandler(directActionRequestHandler);
//session creation
public WOSession createSessionForRequest(WORequest request) {
WOSession session = super.createSessionForRequest(request);
// cookies
session.setStoresIDsInCookies(false);
session.setStoresIDsInURLs(true);
// debug
NSLog.debug.appendln("Application: new session created: " +
session);
return session; }
- Storing IDs in Cookies and the browser does not accept the cookie?
- Not sure with this one: overriding some of the methods involved in
the RR loop without calling super?
Main's AppendToResponse DOES call super.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
