Thanks Dustin, We about to swap onto curl_multi any way, but we could be hitting 1000 api calls from a single page view, without too many problems. We could convert it all to cron but it's a fair amount of work.
Essentially we have a news module, and when a news item is created, we go back to the main view page and send out notifications to all the registered users, via api calls. Regrettably its one call per user, nothing we can do about the api.... No reason why we couldn't add them all to a db and call a cron job to process them all, I was just hoping symfony would have a method to continue processing after the render has occurred. If you have any other suggestions, I'd be keen to hear them Mat -----Original Message----- From: Dustin Whittle [mailto:[EMAIL PROTECTED] Sent: 25 November 2007 14:45 To: [email protected]; Mat Subject: [symfony-users] Re: render page continue processing Mat, You can use curl_multi to parallelize the api calls and reduce latency. Also, if these api calls are not needed as part of the response, then create a cron task. - Dustin On 11/25/07 9:37 AM, "Mat" <[EMAIL PROTECTED]> wrote: > > Is there anyway to send the page to the browser and continue processing the > script in symfony? > > We essentially have a few api calls which slow down our page views, however > the responses from the api calls in no way effect the page being displayed, > we we would like to optimize this. > > Thanks in advance. > > Mat > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
