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 only 4) as the hour clicks over. Although ocasionally this drops a message, it's generally pretty solid. Perhaps because of when I'm sending them, I get in at the start of the allocation.
As far as scalability goes, I would say GAE is really suited for it's read scalability, so if unless your Twitter bot writes are going to massive, then scalability shouldn't be an issue if you move these writes over to a seperate host. I guess a (nasty but possible) pattern would be to have the Twitter interaction come from your host which could act as a proxy, then use App Engine for all the processing and reporting on the data. At least in my application this would be a potential work-around if this becomes an issue. Cheers Tim On Sat, Mar 14, 2009 at 3:57 PM, Richard Bremner <richyr...@gmail.com>wrote: > 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 > wouldn't make it easy to circumvent their limit unreasonably. I do happen to > have a hosted linux server a I can put a proxy script on, I guess I'm lucky > there, but I am using GAE for its scaleability which my server certainly > isn't. I don't need to go into all the reasons GAE is more scaleable than my > own server :-) > If anyone thinks of anything, I'd love to know. > > Rich > > 2009/3/14 lock <lachlan.hu...@gmail.com> > > >> 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 to see if they could build more 'smarts' into their rate >> limiting? >> >> Would be really interested to see if you end up resolving this issue, >> thanks >> for the heads up. Sorry I can't help. >> >> Cheers, lock >> >> On Mar 12, 10:43 pm, richyrich <richyr...@gmail.com> wrote: >> > Hi there, >> > >> > I have been writing a simple little app that uses the Twitter API. It >> > works perfectly on my local development server but it fails when I >> > upload it because I get this error from Twitter: >> > >> > error=Rate limit exceeded. Clients may not make more than 100 requests >> > per hour. >> > >> > ...even though my app only makes 1 request. what is happening is that >> > other people apps must be using the Twitter API from the same IP >> > address. does anyone know a good way around this other than hosting my >> > app somewhere else? >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
