These services, I presume, are throttling usage from each API user. Probably based on IP address as well as just your authentication.
Appspot apps, I believe, share one IP or a limited range of IPs. So you're basically sharing a resource allocation meant for one API user with a bunch of other apps running off the appspot domain. That's my guess anyway. I'd recommend if possible having any data posted to Twitter or Bit.ly or other such services via javascript in the user's browser to get around IP restrictions. E.g. if a user on your site clicks on something and you want to do something on your site and send an update to twitter, then instead of having your app to the latter bit, have it done using AJAX on the user's side. Your use case may not allow for this, but if it does, you should think about doing it that way... On Jan 9, 1:30 pm, neoedmund <[email protected]> wrote: > I wrote a program to use API > ofhttp://api.bit.ly/shortenandhttp://twitter.com/statuses/update.json. it > works well in local pc, > but cannot work in appspot. > bit.ly returns { "errorCode": 503, "errorMessage": "Service > unavailable.", "statusCode": "ERROR" } and twitter ignore the new > message i want to post. > what's wrong ?
-- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
