Matthew Weier O'Phinney-3 wrote:
>
>
> From the above experiments you've tried, it sounds like you want to
> offload some processing to occur after the content is delivered, but
> want it to occur without keeping the connection to the client. With this
> in mind, I'd suggest building a job queue. With this sort of solution,
> you send a message to the queue, and then a queue processor queries it
> periodically and performs routines pertinent to the message sent.
>
> There is a Zend_Queue proposal under review, but not yet accepted. There
> are also commercial solutions such as Zend Platform's Job Queue which
> can perform this work.
>
> You can also roll your own, something I've done before myself. Usually,
> you provide a callback, and the arguments for the callback, and your
> queue processor then does the processing. I've done implementations that
> used static class methods for the callbacks, as well as some that would
> instantiate the given class and then call the given method with the
> provided arguments (utilizing call_user_func_array()).
>
>
Hi Matthew,
Thanks for your reply. Sounds great, just as some background - what I am
doing is uploading results from a race in my racing simulator - writing them
to the db and then I am intending to do some processing to figure out if
anyone broke any records or passed any milestone (1000 laps for example).
I haven't been using PHP very long, so forgive me the silly question, but
what form would a queue processor take? Is it a php script run as a daemon?
Is there a way for Zend to kick it off if it isn't running already?
Thanks again for your help
All the best,
Ash
--
View this message in context:
http://www.nabble.com/Continue-Processing-after-an-action-is-completed-tp21900147p21902316.html
Sent from the Zend Framework mailing list archive at Nabble.com.
