Google Calendar API DoS prevention

It appears that the Google calendar API effectively locks you out if you create and delete a few (le开发者_开发技巧ss than 10) calendars within a short space of time.

This has made it basically impossible for me to test my app, because it creates/deletes a calendar for each user that is added/removed from the app. Currently, I'm "working around" this issue by creating a new Google account each time I get locked out of the Calendar API. Clearly, this solution is less than satisfactory.

Is there any way I can avoid this over-zealous DoS prevention?

Thanks, Don

---

If your application doesn't require an instantaneous call out to the Google API, your code can queue the actions and throttle the calls to x calls over y seconds. Not an ideal solution but it would reduce the likelihood of hitting the quota limit.

---

Can't you just "reset" (i.e. delete all entries) the test calendars instead of re-creating them every time?

---

Try creating a localized version of the calendar that you either have the user save (upload to Google) with a button click or as an event (ie. closing the program, every x minutes). Store all the data locally, and only upload to Google as needed. I don't know how neccessary it is that the data be available immediately, but if your app can handle some delay, then this may work for you.