• 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: JavaClient session timeout?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JavaClient session timeout?


  • Subject: Re: JavaClient session timeout?
  • From: Stamenkovic Florijan <email@hidden>
  • Date: Mon, 30 Mar 2009 13:27:02 -0400


On Mar 30, 2009, at 13:18, David Avendasora wrote:

This is the approach I was thinking of. Have the client keep track of how long since the last server communication (I have no idea how to do that...) and set a timer based on the session timeout value. It's only job would be to give the user a few minutes warning to finish what they were working on, extend the session (if possible, a ping as you describe below would be perfect) or quit.

Hm, might be easier then I thought, using:

http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/com/webobjects/eodistribution/EODistributionContext.Delegate.html

Most definitively something worth looking into at some point. Also, this strategy is not exclusive of the constant-ping strategy, so I might provide both in WOJCKit at some point. Will put it on my to-do list.

Another approach I considered at some point is to have the client "ping" the session at small intervals. Now, this should be fairly easy to do, and should ensure that the session never expires. There are some potential problems with this:
- multithreading: the "ping" of course will get scheduled on another thread, which EOF might not like. One could schedule it to happen on the EDT, but that might result in an occasional glitch in the GUI. Or, maybe if using a stateless RMI method for the purpose of the ping, this would not be a problem
- session accumulation on the server: not sure what the implications of this could be.

The biggest draw-back I see here is the longer the session hangs around, the more stale the data is getting. In short, you are making things easier for the user, at the expense of a lot of time and care making sure that your client-side application has fresh data. It could be worth it, but maybe not.

Yeah, data freshness is a major pain in the ass. Honestly, unless it is really, and I mean *really* important to the client to constantly have super-fresh data, I am happy to live with it getting a few hours stale.


F
_______________________________________________
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: 
 >JavaClient session timeout? (From: John Huss <email@hidden>)
 >Re: JavaClient session timeout? (From: David Avendasora <email@hidden>)
 >Re: JavaClient session timeout? (From: Stamenkovic Florijan <email@hidden>)
 >Re: JavaClient session timeout? (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: OT: Thumbnail image of webpage
  • Next by Date: Re: OT: Thumbnail image of webpage
  • Previous by thread: Re: JavaClient session timeout?
  • Next by thread: OT: Thumbnail image of webpage
  • Index(es):
    • Date
    • Thread