Any other solutions available for app engine folks stuck out here? Please help!
I'm noticing this exact problem as well. I'm making only a few requests per hour. I have tried setting the user-agent but it did not help. Akshar On Oct 6, 9:50 am, Chad Etzel <c...@twitter.com> wrote: > Hi All, > > GAE sites are problematic for the Twitter/Search API because the IPs > making outgoing requests are fluid and cannot as such be easily > allowed for access. Also, since most IPs are shared, other > applications on the same IPs making requests mean that fewer requests > per app get through. > > One work around would be to spin up a server in EC2 or Rackspace Cloud > or something and use it as a proxy for your requests. That way you > have a dedicated IP that will have its full share of resources talking > with the Twitter servers. > > HTH, > -Chad > > > > On Tue, Oct 6, 2009 at 12:45 PM, Martin Omander <moman...@google.com> wrote: > > > Same here; my app runs on Google App Engine and 40% of the requests to > > the Twitter Search API get the 503 error message indicating rate > > limiting. > > > Is there anything we as app authors can do on our side to alleviate > > the problem? > > > /Martin > > > On Oct 5, 1:53 pm, Paul Kinlan <paul.kin...@gmail.com> wrote: > >> I am pretty sure there are custom headers on the App Engine that indicate > >> the application that is sending the request. > > >> 2009/10/5 elkelk <danielshaneup...@gmail.com> > > >> > Hi all, > > >> > I am having the same issue. I have tried setting a custom user-agent, > >> > but this doesn't seem to affect the fact that twitter is limiting > >> > based on I.P. address. I'm only making about 5 searches an hour and > >> > 80% of them are failing on app engine due to a 503 rate limit. > >> > Twitter needs to determine a better way to let cloud clients access > >> > their search API. It seems like they have really started blocking > >> > search requests in the last week or so. > > >> > If anyone has any idea about how to better identify my app engine app > >> > please let let me know. > > >> > On Oct 5, 2:59 am, steel <steel...@gmail.com> wrote: > >> > > Hi. I have this problem too. > >> > > My application does two request per hour and it get "rate limit". > >> > > What is wrong? I think it is twitter's problems.... > > >> > > On 1 окт, 01:45, Paul Kinlan <paul.kin...@gmail.com> wrote: > > >> > > > Hi Guys, > >> > > > I have an app on the App engine using the search API and it is > >> > > > getting > >> > > > heavily rate limited again this past couple of days. > > >> > > > I know that we are on a shared set of IP addresses and someone else > >> > could be > >> > > > hammering the system, but it seems to run for weeks without seeing > >> > > > the > >> > rate > >> > > > limit being hit and then all of a sudden only about 60% of the > >> > > > searches > >> > > > I perform will be rate limited. This seems to occur every two months > >> > or so. > > >> > > > Has something changed recently? > > >> > > > Paul
