On Wednesday, Aug 27, 2003, at 14:22 US/Pacific, Octavian Rasnita wrote:
Or if you don't want to depend on Unix's cron and want your program to do[..]
everything, you can set it so each time a new visitor comes to your site,
checks which files are not needed, and delete them.
You can use fork to avoid putting the visitors to wait until the program is
doing its background job.
at first blush that CAN seem to be an interesting idea - but in the worst case one can have N connections, each of which has generated N forked children to walk through M possible files... and one starts asking one's self,
is this an order N square or N factorial solution?
while in the worst case the cron job based solution is merely an order N problem...
ciao drieux
---
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
