• 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: only one login per user
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: only one login per user


  • Subject: Re: only one login per user
  • From: Tony Becker <email@hidden>
  • Date: Tue, 22 Jun 2004 11:32:47 -0400

Upon login store the sessionid, the requestid, and the login time. On logout, null them.
On login, check for the existence of the sessionid/requestid within a reasonable time (your choice).
Allow them in if the time difference is > 1hr or so.
If the time difference is less then 1hr, give them a choice of the old session, or trashing it (you have the keys in the DB) and creating a new session.


http://developer.apple.com/documentation/WebObjects/Reference/API5.2.2/ com/webobjects/appserver/class-use/WOSession.html


Note that there may be additional EO/DB clean up, if the previous session was in some kind of transaction, so maybe restoration might be something to try (If they simply closed the browser. Also, how would you prevent two people, with the same login from "fighting" for the "singleton" session - maybe the 1hr should be the session timeout and you force them to wait.


Food for thought - I don't know your application requirements.


On Jun 22, 2004, at 10:39 AM, Nathan Dumar wrote:

I would like to make sure a user account is not used by multiple people at the same time, by checking to see if the user has already logged in (has an active session). I can see two possibilities so far, but my knowledge falls short with both ideas:

1) Store the info in the db and override the session.terminate() to set a user to logged out (in case they don't log out, but the session times out). How and where do I override session.terminate()?

2) Put a function at the application level that checks each session's user variable (across all app instances) for the proposed user. How do I phrase the WOApplication-level code to look down into each session? How do I call this code from a page?

Is there a better way that I'm missing?

Thanks for your time.
Nathan
_______________________________________________
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.



Tony Becker
Cell: 727 460 1891

"The best proof that there's intelligent life in the universe is that it hasn't come here." Arthur C. Clarke
_______________________________________________
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.



  • Follow-Ups:
    • Re: only one login per user
      • From: Nathan Dumar <email@hidden>
References: 
 >only one login per user (From: Nathan Dumar <email@hidden>)

  • Prev by Date: Re: Duplicate records
  • Next by Date: Css generation question
  • Previous by thread: only one login per user
  • Next by thread: Re: only one login per user
  • Index(es):
    • Date
    • Thread