This hasn't proved to be much of a problem, and the team we now work with has been really great about setting up data sources, verity collections, debugging IP's and scheduled tasks. But that can't last. They've asked me to try and find a better way to handle scheduled tasks, and since we use a newsletter system which relies on them, this is somewhat of a high priority for me.
My first step is to eliminate scheduled tasks from as much code as possible - newsletters will get sent when you click 'Go' from now on. We can all live with that. But my question is whether or not anybody can think of an alternative for those times when a scheduled task is just necessary? (For example, I have one run at 1 am every morning to update a verity index, and will need one to run every morning to send out snow conditions for a local ski mountain.)
Any thoughts? - Ken
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
