you funnel your events into a queue and fetch one off the queue whenever a process finished with the previous one. this is exactly what you do with your query. you have data, you pick one, you process it, you update and pick the next record.
event queues are built for batch processing, actually only with batch processing in mind ... On Tue, Jan 27, 2009 at 10:01 AM, speed3r <[email protected]> wrote: > > Would you use an event queue for batch processing? Not sure how > useful that is... > > > On Jan 26, 4:22 pm, lenz <[email protected]> wrote: > > ever thought of using an event queue? looks much like a problem solved in > > the past already. using mysql for it might not be the best approach > though. > > look at amazon simple queue or something comparable, it would be a way > > better fit i guess.push requests to a queue and only store the results in > > the DB ... > > > > -- iWantMyName.com painless domain registration (finally) --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
