Re: Session timeout notifications
Re: Session timeout notifications
- Subject: Re: Session timeout notifications
- From: John Pollard <email@hidden>
- Date: Mon, 27 Oct 2008 18:25:25 +0000
This session is no more! He has ceased to be! 'E's expired and gone to
meet 'is maker!
Thank you Chuck, recording the session id is the answer.
On 27 Oct 2008, at 18:03, Chuck Hill wrote:
On Oct 27, 2008, at 10:43 AM, John Pollard wrote:
Hi list,
When a SessionDidTimeOutNotification is received, the
NSNotification passed to the callback has an object() passed that
is a String rather than the Session that issued the notification
(strange?).
No, the session has timed out so it no longer exists. At least I
suspect that is the theory.
How should I convert that string (the session ID?) to the
underlying Session object?
Or should you?
Background: I am trying to keep track of sessions per IP address in
the Application class so that I can avoid any one IP running wild
with Sessions (rogue bots). I therefore need to get a handle on
each Session that times out.
Why record the sessions in the Application? Is recording the
session ID per IP not sufficient?
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden