Re: Java Monitor Sessions Question
Re: Java Monitor Sessions Question
- Subject: Re: Java Monitor Sessions Question
- From: Art Isbell <email@hidden>
- Date: Wed, 28 Apr 2004 16:15:18 -1000
On Apr 28, 2004, at 3:41 PM, James Cicenia wrote:
> Ahhh very interesting. I use no DirectActions, at least not explicitly.
Then a Session will be created for you when a new user accesses your
WO app.
> But, I do hit session a lot! Half my app uses the current selection all
> the time. Heck I even thought it was encouraged being as it is always
> the default object in WOBuilder.
>
> I have the current portfolio, project and user in session and access
> them via ((Session)session()).user();
>
> What is the proper approach here?
Nothing wrong with this unless you are throwing things into your
Session object that could easily be passed from one component to the
next. But this won't cause extra Sessions to be created.
Unless you are explicitly destroying Session objects (e.g., when a
user signs out of your app), Sessions will remain until an inactivity
time-out occurs. The default time-out period is 1 hour. So if you
continue accessing the main URL of the same app process multiple times
within an hour, each created session will continue to exist.
If this doesn't explain the number of active sessions, then logging
when each session is created as has been suggested would be a first
step at debugging the problem.
Aloha,
Art
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.