Maybe use delayed jobs and workers to pull this from twitter in the background so you don't freeze the dynos?
K. --- http://blitz.io http://twitter.com/pcapr On Fri, Mar 25, 2011 at 9:26 AM, Moso <[email protected]> wrote: > I'm using the APIGEE plugin, and it's great. > Problem is, calling the Twitter API is blocking. And when Twitter is slow, > my number of concurrent requests drops through the floor. > I'm using caching, and even some prefetching. But wondering if there is > anything I could be doing specific to the way I call the API? Is there a way > to design my app so that it's using callback events from APIGEE instead of > blocking calls? > For context, my app needs to pull user data from Twitter. This can't be done > from the client, for a few reasons. Client calls the server, server calls > Twitter. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" 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/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
