Hi Michael! I'm facing the exactly same problem! Did you find a way to post the whole calendar at once?
Thanks a lot! Rafael Dantas On Jan 14, 7:25 am, Mikado <[EMAIL PROTECTED]> wrote: > Hi, > > Thanks for the reply. I guessed it was an anti-spam system, and when > looking through my code, I realized it's definitely not optimized > (that's often the problem of self-learning, and also I think quite > some possibilities of the calendar API have been added). To explain > the general idea of what I do, I extract from a project management > software (that runs on our network) some tasks and their assignments > to Google Calendar, so as to give users an external web view of their > planning from any terminal with an Internet connection. My > architecture is the following : > I got a "main account" with X subcalendars (atm X should be around 20) > and I share these calendars to personnal accounts of these X people. > This way I can simulate a kind of "admin view" and I can control that > these datas are not modified (the source system is considered as the > reference). > > Atm, I first delete some likely to change events, then recreate them. > That part could created a big overcost and may explain this hitting > the limitation. What I'm actually surprised of is that it worked > actually fine before. Did you change the limitation of operation a > day, or is that a newly implemented system ? Or was it simply that > from one day to the next one, since the source of my datas grows a bit > bigger with each day, I hit this limitation ? (for the exact number of > operation, I got actually no clue, I don't know enough what is > considered as operations from your API ; if so, I could try to track > that to see how much operations I actually perform). > > In any case, I dunno if I'll be allowed to do it, but I do not like > the idea of being close to a limitation, first because it implies my > operations are spamming the server somehow, second because it means my > application could stop working anytime, so I'll try to find some spare > time to redevelop it somewhen, the problem being this somewhen could > be in quite some time, and I need to have this thing work again soon. > Thus my following questions : > > - if I use the batch system to gather my operations by group of 50 or > so, would it consider that I do 50 times less operations, or would > each of them still be considered as an operation on events ? (would be > an emergency solution) > > - what is exactly considered as operations in the limits ? > modification requests only, or read requests too ? (if so, I might do > too much of them too). > > - And finally, is there a possibility to insert kinda a "whole" > calendar in one operation ? My first idea back then was to retrieve > the content of every calendars, map them in memory, do my > modifications and sending back to the server the modified calendars. > Is there any simple way to do that directly or indirectly with the > API ? (maybe through some iCal or xml or anything of that kind ?) > > Or is there maybe a "white paper" on how to develop and/or optimize > developments without completely spamming the server ? > > Thanks in advance for the replies and sorry for the "spamming", > > Regards, > Michael SARTON. > > On 11 jan, 19:20, "Austin (Google)" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > It appears that you have hit the quota limitation for the day. Google > > Calendar Data API has a quota limitation on the number of operations > > permitted for the day, this is in place to guard against potential spam or > > abuse. Can I ask what operations are you performing to hit this wall and > > how many of them are you trying to do? > > > Thanks, > > Austin > > > On Jan 11, 2008 2:12 AM, Mikado <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I've been using Google Calendar API a bit in the past months, to > > > develop a small application that transfers some data from some > > > planning application to Google Calendar. > > > It has worked so far, but since a few days, I receive the following > > > error message (stack trace included) : > > > > com.google.gdata.util.ServiceForbiddenException: Forbidden > > > User has modified too many events today. Please try again tomorrow. > > > > at > > > com.google.gdata.client.http.HttpGDataRequest.handleErrorResponse(Unknown > > > Source) > > > at > > > com.google.gdata.client.http.GoogleGDataRequest.handleErrorResponse > > > (Unknown > > > Source) > > > at > > > com.google.gdata.client.http.HttpGDataRequest.checkResponse(Unknown > > > Source) > > > at com.google.gdata.client.http.HttpGDataRequest.execute(Unknown > > > Source) > > > at com.google.gdata.client.http.GoogleGDataRequest.execute(Unknown > > > Source) > > > at com.google.gdata.client.Service.delete(Unknown Source) > > > at com.google.gdata.client.GoogleService.delete(Unknown Source) > > > > Does it mean I probably do something wrong that would do way too many > > > operations ? What is the limit of operations one user can do each > > > day ? If I use the Batch system (that didn't exist when I wrote this) > > > would it solve the problem (or more exactly : does one batch call > > > counts as one modification, or does it count still as X operations ?). > > > If this cannot be solved through the Batch system, is there any way to > > > work around that ? > > > > Thanks in advance for your replies, > > > Regards, > > > > Michael Sarton. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
