On Sat, Jul 5, 2008 at 6:01 AM, Waynn Lue <[EMAIL PROTECTED]> wrote:
> I have a system where a user clicks on a button which causes rows to
> be inserted in to the database. I'd also like to run some lengthier
> post-processing on those rows, but don't want to put it in the
> critical path of the rows being inserted and returning to the user.
> What's the best way to either batch up these other actions, or pass
> them to a thread or other asynchronous process to do the second part
> of the action?
Can you just run this via a cron or Scheduled Task? Just have a
boolean column that distinguishes new rows as unprocessed, and flip
the flag when the cron script processes the row.
--
</Daniel P. Brown>
Sent from an airport terminal in Cincinnati Airport, waiting for a
flight back to Scranton, Pa.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
