Google Calendar API DoS prevention -


That means you lock the Google Calendar API effectively, if you have some (less Less than 10) create and delete calendars

It has made it virtually impossible for me to test my app, because for each user connected / removed from the app, one The calendar creates / deletes. Currently, when I step out of the Calendar API, I am "working" on this issue by creating a new Google Account every time, this solution is less than satisfying.

Is there any way I can avoid the prevention of this super-enthusiastic dose?

Thank you, Don

If your application does not require an immediate call For Google APIs, your code can queue functions and can scrape x more than x seconds calls. Not the ideal solution, but it may be less likely to kill the quota range.


Comments