• 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: "Jerry W. Walker" <email@hidden>
  • Date: Mon, 30 Jan 2006 16:23:34 -0500

Hi, Norberto,

I don't think you can establish sessions that don't time out. However, if you set Session timeout to several days, it has the same practical effect.

At my last company, we had a couple internal applications that required logins. Rather than keeping sessions from timing out, we provided cookies for both the loginID and encrypted password if requested (by a checkbox on the login page). We reset Session timeout to about 18 hours, if I remember correctly, using WOApplication's setSessionTimeOut() so if we had a session running when we left in the evening, it would still be running the next morning when we came into the office.

If you didn't access the application within the 18 hours, of course, your session would time out, but the next time you accessed the application, if your browser had a legitimate set of cookies, the app would log you in automatically. You might lose any work that you had left and not saved for over 18 hours. But that was typically not a problem, since if you hadn't accessed the app for over 18 hours, you were probably not actively using it anyway.

We recognized that this approach was not particularly secure, but that was ameliorated by the fact that neither application had particularly sensitive data and that all our workstations timed out quickly requiring a login to start using the work station again once the screen saver started.

Regards,
Jerry

On Jan 30, 2006, at 3:59 PM, 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) ?

Are there any suggested strategies ?

Thanks

--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems


    email@hidden
    203 278-4085        office



_______________________________________________
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: Easy question I hope
  • Next by Date: Re: EnterpriseObjects in a regular Java application
  • Previous by thread: Sessions
  • Next by thread: Re: Sessions
  • Index(es):
    • Date
    • Thread