The parent process would be examining data in a database and moving it around to where it needs to be... then signifying to the child processes what needs to be done. the child processes would only touch the part of the database assigned to them by the parent process... the point is to have one 'queen ant' directing the work, and many 'worker ants' working together to accomplish their goals...
On Thu, 2002-06-27 at 07:47, BB wrote: > what would the adult/child be doing? > > "Apokalyptik" <[EMAIL PROTECTED]> wrote in message > 1025128477.26152.23.camel@BlackHole">news:1025128477.26152.23.camel@BlackHole... > > I'm the author of a little used, little cared about ftp indexing script > > (http://www.apokalyptik.com/ftp/) and i'm working on - slowly - > > releasing version 2.0. Version 1 runs as a cron job (or a daemon) and > > its one monolithic piece of code that handles managing of the queue of > > new and old sites to be scanned, as well as the scanning of these > > sites... > > > > In version 2 I'm looking to seperate these functions into seperate > > mother/daughter daemon processes, and I'm not sure whether it's worth > > the time messing around with the process forking functions in php, or i > > should just make truly seperate file/processes... > > > > Any input would be greatly appreciated. > > > > Thanks in advance! > > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
