On Dec 1, 2008, at 6:01 PM, Mike Schrag wrote:
Why doesn't terminate check in the session?
It does check in the session, but because it has terminated, the
request that is blocked on the session checkout never gets unblocked.
If it checks in the session, it should .notify() the TimeoutEntry
(the code looks relatively straightforward)
Won't a terminated session .notify() the TimoutEntry?? That's
asinine. This is cruising for a Wonder fix, I think.
I really doubt that you could do this.
hmm...
I took the easier, if far less elegant route, of setting the
session timeout to a few seconds. That way any queued requests
pass through the RR loop. To make this a little "safer", I also
null the user and do other cleanup on the session so that any
further requests will just get an error page or a login request.
Sketchy. I must be missing something here, because this seems
totally fixable to me.
I dunno, think you are up to it?
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
