• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Sessions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sessions


  • Subject: Re: Sessions
  • From: Art Isbell <email@hidden>
  • Date: Mon, 30 Jan 2006 12:11:59 -1000

On Jan 30, 2006, at 10:59 AM, Norberto Menendez wrote:

How is it that you establish sessions that don't time out in WO (for an application with a small number of users < 50) ?

WOSession's setTimeOut() method takes a double as the number of seconds argument. I believe that if you calculate the time interval that the largest double would represent, it would be considerably longer than the time interval since the Big Bang :-) If you manage your WO apps using JavaManager, you would need to set the session time out to a very large value in JavaMonitor. So that should solve the problem of session inactivity time-outs :-)


But do you really want to do this? JavaMonitor won't be able to restart an instance unless the number of active sessions equals the minimum active session count (0 by default). If you set the minimum active session count to a number larger than the maximum number of sessions you expect to be active, then the instance will restart when scheduled. However, in doing so, you might pull the session out from under a truly active user which usually isn't cool. Maybe you could inform your users that periodic maintenance would occur which would restart your app at a time of very low user activity.

If you don't restart instances periodically, each instance could gradually increase its memory usage which could negatively affect performance. This is especially true if the app fetches objects from a database. A cached object snapshot will not be freed as long as a reference exists from an editing context (e.g., WOSession's default editing context). So your app can gradually fetch an entire database into its cached snapshots if users fetch a variety of objects.

Aloha,
Art

_______________________________________________
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


References: 
 >Sessions (From: Norberto Menendez <email@hidden>)

  • Prev by Date: Re: EnterpriseObjects in a regular Java application
  • Next by Date: Re: Easy question I hope
  • Previous by thread: Re: Sessions
  • Next by thread: Re: Sessions
  • Index(es):
    • Date
    • Thread