It was discussed in
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01851.html
Thanks. I knew someone would find it!
which has a link to a lengthy article with sample code. The lengthy article says the forked child would update a session cache and the parent would continuously check the cache to see if the child completed. Wouldn't it be more straightforward for the parent to perform a "waitpid"? When the child exits and the parent receives notice of this event (via waitpid), it could proceed to check the session cache for more detailed information about the final disposition of that process.
No, I'm pretty sure that won't work. If the parent is waiting for the child to finish, then it has to maintain a connection to the browser the whole time while the child is running. This won't work since we want to return a 'please wait' screen and most browsers would time out anyway.
Also, if the parent is waiting on the child, the parent can no longer serve any more requests for other users. We would be tying up the resource while it isn't doing anything. It really wouldn't be any different than if the parent had done the processing it self.
Michael Peters Developer Plus Three
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
