Alain, The reason that I have a poll going out every minute is that the gadget needs to check for when an event has already passed. In essence, the user selects a couple of events to watch, and the gadget would display that those meetings haven't occurred yet. This needs to watch for when some of these events do occur, and react to that. We're working on one of many ways to do this same check without polling Google incessantly, but I'd still like to make sure that through regular usage this limit isn't hit.
How high is the limit, exactly? Or even generally? Like I said, I'd like to be sure that the users of the gadget wouldn't hit that limit on regular usage. Also, I'd like to know if the limit is just for Google Data API calls, or for any Google APIs, or any calls to any external servers. Lastly, I just wanted to get your opinion on what else could cause this 403 error to keep crawling up. Are there any other triggers for Google to return 403 to a request for information? Unfortunately, the error doesn't give any other explanation, so I'm left guessing at this point. Thanks a ton for the help! I definitely appreciate it. --Mark -- 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://code.google.com/apis/calendar/community/forum.html
