I think the issue here is that user will never return. So struts dude needs some kind of mechanism to check every so often to see if the user has not returned in 24 hours. If the user has not came back, he wants to delete that record.
So some timer mechanism is needed. His options.. Use resin application server and use the run-at attribute for a servlet. You can schedule it to run every hour or 30 mins or whatever. Or use JDK's Timer or Quartz from open symphony. Or JMS.. I think quartz makes sense over here. My dos cientos (again) Pritpal -----Original Message----- From: Michael Finger [mailto:[EMAIL PROTECTED] Sent: Thursday, August 19, 2004 10:29 AM To: Struts Users Mailing List Subject: RE: Help on Action implementing thread for checking user registration thru email? I second the below - when you pull the user info from the database check the timestamp and in it's greater then 24hrs, delete it and kick the user out... then you can just cleanup the database daily, weekly, etc at off peak times... this way nothing is dependent on a job running... Mike -----Original Message----- From: Daniel Perry [mailto:[EMAIL PROTECTED] Sent: Thursday, August 19, 2004 10:15 AM To: Struts Users Mailing List Subject: RE: Help on Action implementing thread for checking user registration thru email? To do what you require, instead of scheduling a job for each entry after 24hrs, i would include a timestamp in the database, then say every hour, check for expired entries and delete them. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
