Oh yeah, you can maintain progressive status on multiple "tasks" in all the cron jobs/dbs, and then make pretty graphs for the user to look at as they check back in to see how far along things are. I do that a lot -- A few minutes of coding for eye candy for the suits does wonders sometimes... Plus, it provides and easy way for you to make sure that the cron jobs are actually running and doing something. On Tue, July 11, 2006 10:06 am, John Gunther wrote: > Great approach! Slicker'n snot. I added one enhancement: The shell > script writss progress info to the database which the trigger page > displays on entry. > > > > Richard Lynch wrote: >> I would recommend, however, that you re-structure things slightly so >> that the Architecture is more like this: >> >> User visits web page. >> Page generates a database record of what needs to be done. >> Page finished. >> >> >> CRON JOB: >> Look in task list of what needs doing, and do some of them. >> Make sure only one job is done at a time, or whatever race >> conditions >> are handled here. >> >> I've done projects both ways, and always end up frustrated with the >> "PHP attempts to background a process" and the "Task List + Cron" >> always works out far far better. >> > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
