From: Matthew J. D. <mda...@se...> - 2003-07-16 00:30:06
|
> This approach has the disadvantage of building all the functionality > into one > big script. There may be an advantage in that the parent process can > act > as a nanny for all the children, reforking a new one if a child dies or > automagically killing them if they live too long. Dean, One thing to remember is the tasks need to do other things beside answer calls. i.e. If someone looks at all their messages on the computer the message waiting light needs to go off their phone. Some process that is doing the syncronization will have to tell one of the threads they need to go off hook and dial the MWI code, or to notify someone on their pager. We need to devise a way for one of the scripts to be able to break out of its loop while it is waiting for a call. It could be as simple as they all continualy check a test file for something to do, they would delete the entry so no other scripts will duplicate it, if successful it would write it to a log, on a failure it would write it back to the "jobs" file/database. It could also be a mother script passing out assignment via tcp-ip. Something to think about. -Matt |