Thanks Tim.
Think I've managed to convince myself that I can work around the
lack of inbuilt scheduled tasks. Who knows by the time I manage
to pull together enough motivation google may have implemented
it already. Worst case I may be able to use a work server to call
an URL, although its not
Ahh! Yes, by google search API I meant Twitter search API!
I'm using a CRON job to trigger a special URL every 5 minutes. Originally I
had this job on my own webhost, but I breached the terms of service because
a) sometimes the way I update the trend lists can take a long time and the
very basic
Interesting,
I have a Twitter app (http://twendly.appspot.com) but I don't seem to be
having this issue at the moment. However, while I read information every 5
minutes from the google search API (which is rate limited differently) I
only send a few messages (no more than 5 or 6 max and usually
I could think of a rather simple solution for twitter: Just give
everyone an API key that they use to authenticate, and make the limits
based on the key instead of the IP addresses. No?
On Mar 14, 12:57 am, Richard Bremner richyr...@gmail.com wrote:
Hmmm yes this is a difficult one. Neither
That would work, and some Twitter API calls are authenticated already, but I
guess it would be easy to bypass the limit by registering for multiple keys
and having your app vary which key it uses. Maybe that doesn't matter in the
big picture though.
rich
2009/3/15 MajorProgamming
Hi Tim,
I presume GAE requests can come from a large number of different IP's. My
app has been working fine for months, but then I made a small change, did an
upload and it suddenly stopped working with this error, so I can only assume
my app started coming from a different IP due to that upload,
Hi Tim,
Just had a look at Twendly, looks good! I've just got a few quick
questions, if you wouldn't mind...
1. By 'google search API' you actually mean 'twitter seach API',
yeah ? ;-)
2. How do you go about pulling data from twitter every 5 minutes?
Unless I'm missing something there are no
You could host one script on an other server that works as a proxy for
your requests to twitter.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
Hmmm. My next app engine project _was_ going to be an app that relied
on twitter. This doesn't sound good. As per your situation the app
wouldn't
hammer twitter, one request to the search API every 5-10 minutes or
so.
Given its not exactly an app engine problem did you try contacting
twitter
Hmmm yes this is a difficult one. Neither Twitter nor Google are being
unreasonable, and each GAE developer is probably performing a sane number of
Twitter API requests but combined we are ruining it for everyone. Ohhh the
solution? I can't think of a good solution Twitter could implement which
10 matches
Mail list logo
