Chad,
Sorry for not being clear. I was thinking about Abraham William's
suggestion above where Twitter Search API works with authenticated
sessions+rate limiting, instead of IP based rate filtering. Just so
you know, AppEngine has 30 second timeout on request to all AppEngine
urls, and 10 second
On Sun, Oct 18, 2009 at 8:09 AM, vivekpuri wrote:
>
> Will someone from Twitter please respond if there is an ETA to resolve
> this issue. Work arounds can never be really as effective as the real
> deal.
Sorry, I thought it was clear from the previous email. There is no ETA
because it's not goi
Will someone from Twitter please respond if there is an ETA to resolve
this issue. Work arounds can never be really as effective as the real
deal.
I would recommend just using a physical server and uploading a simple
php proxy script. If you have existing webspace, it will save you the
trouble of setting up an complete ec2 build just to run a proxy
script.
On Oct 9, 7:11 pm, Akshar wrote:
> Thanks Abraham.
>
> Any pointers on how to setup
Thanks Abraham.
Any pointers on how to setup a proxy on amazon ec2 for GAE?
On Oct 8, 6:07 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Pretty much. You have limited options:
> 1) Run your Search API requests through a proxy where you will have
> exclusive access to the IP.
> 2) Wait for V2
Pretty much. You have limited options:
1) Run your Search API requests through a proxy where you will have
exclusive access to the IP.
2) Wait for V2 of the Twitter API where the REST and Search APIs get
combined so you can have authenticated search queries.
3) Hope Twitter slaps some duct tape on
http://apiwiki.twitter.com/Rate-limiting states that "for cloud
platforms like Google App Engine, applications without a static IP
addresses cannot receive Search whitelisting."
Does that mean there is no way to avoid getting HTTP 503 response
codes to search requests from app engine?
On Oct 8,
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 wrote:
> Hi All,
>
> GAE sites are p
I have solved a problem like that:
While I receive an error 503 - my application continue knocking to
twitter with query.
Everything works ;)
Twitter should really in this case either white list all GAE IPs (I'm
sure an email to Google could get all IPs they use) or allow charging
API requests to an authenticated account rather than by IP (much like
the REST API does). This way each GAE application would just set up a
twitter account an
I am also facing this issue. I'm only making a couple of requests
from GAE (about 3-4) and none of them are getting through, I keep
getting the following using Twitter4J
Twitter Exception while retrieving status
twitter4j.TwitterException: 400:The request was invalid. An
accompanying erro
Hi Chad,
I am sorry but that doesn't even help in the slightest.
You are essentially saying that we shouldn't develop on the App
Engine, since would now have to also buy a proxy. Which is completely
unfeasible and defeats the purpose of why people are using the app
engine.
I understand that th
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 w
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 wrote:
> I am pretty sure
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
>
> 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
> bas
I'm noticing this problem as well. I'm making only a couple requests
per hour. I have tried setting the user-agent and the HTTP_REFERER
headers to a custom name, but Twitter doesn't seem to care.
On Oct 5, 2:59 am, steel wrote:
> Hi. I have this problem too.
> My application does two request p
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 det
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 wrote:
> Hi Guys,
> I have an app on the App engine using the search API and it is getting
> heavily rate limited agai
18 matches
Mail list logo
