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]
