This cron job is fairly resource intensive, as it has to check all .ca domains that have not been completed. On average, there are hundreds of .ca domains in this state, if not thousands. And CIRA (.ca provider) is not known for blazingly fast responses.
Sure it would be possible to run this job 2 or (maybe) 4 times a day. Would that really satisfy end-user that is in a hurry? Force button gives customer immediate resolution, anything else would be second rate. Keep in mind that this is just one job out of hundred(s) necessary to run the system: manipulating/storing logs, transfers, renewal notifications, renewals, dequeuers, statistics, audits, all sorts of check and balances, internal reports, etc. Therefore, moderate increase in frequency is an option, but running it every hour is not. Moderate increase in frequency (in my mind), would not be a real solution, hence the button. Regards, Zeljko Dimic Technical Product Manager Tucows Inc. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roger B.A. Klorese Sent: Friday, June 25, 2004 12:31 PM To: Zeljko Dimic Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Request: CA registration process speedup Zeljko Dimic wrote: > We have improvement related to this issues scheduled for next maintenance > release (hitting production towards the end of September). This will be a > button to force check with CIRA, similar to .ca transfer process. But won't it take you about 5 seconds of work to change the cron job to run once an hour, or 15 minutes, or 5? Does the job run for so long or use so many resources as to make this inappropriate?
