|
From a workload management perspective, I think I'd schedule a daily job, running in low priority batch, rather than leaving a high priority Web application active around the clock - a waste of space.
----- Original Message ---- From: RPower@xxxxxxxxxx To: Java Programming on and around the iSeries / AS400 <java400-l@xxxxxxxxxxxx> Sent: Wednesday, June 21, 2006 12:34:07 PM Subject: Thread question I have a need for a web application that I'm writing to do a daily check for expiry dates, and if any meet criteria, to email people notifying them of the expiration coming up. I'm currently creating a thread, then making it sleep for 24 hours and run again. Is this efficient to do? Should I be wary of anything by doing this? Or is there a better way to do it? Ron Power Programmer Information Services City Of St. John's, NL P.O. Box 908 St. John's, NL A1C 5M2 709-576-8132 rpower@xxxxxxxxxx http://www.stjohns.ca/
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
