Tech Forum

On Tuesday evening calendar 2.2.1 was updated to rev 3507 which includes fixes for the calendar sync functionality. The new changes include throttling of the sync requests. The minimum amount of sync requests allowed is once per hour. Additional requests within that time frame will generate a response that represents there have been no changes. This is the minimum allowable value. The calendar app to which you are syncing (like Google Calendar) may in reality sync much less often than that. Please take a few minutes sometime today to verify that your sync functionality is now working as expected by checking your external calendar apps.

Thank you for the patience and support you demonstrate each day here on the forum. It means a great deal to the calendar team to know there are many users willing to try out what we've put together and provide us with meaningful feedback. As always if you see any unexpected or weird behavior please let us know here on the forum.

The synchronization is functioning correctly now with iCal, Lion version 10.7.4. Thank you very much!

kyleq wrote:The minimum amount of sync requests allowed is once per hour.

Nit-pick: Is that a maximum or a minimum? (Maximum frequency, minimum sync interval)

Either way, thanks for getting it fixed!

kyleq wrote:OAdditional requests within that time frame will generate a response that represents there have been no changes.

Are you sure about that? In my experience, additional requests less than an hour after the last successful request return no data at all. That tends to be treated as an error by most calendar applications, since it is not a valid iCal (.ics) file.

aebrown wrote:Are you sure about that? In my experience, additional requests less than an hour after the last successful request return no data at all. That tends to be treated as an error by most calendar applications, since it is not a valid iCal (.ics) file.

It returns an empty result but the HTTP return code is 304 which is used to indicate that a page has not been modified (although it's usually used in connection with the If-Modified-Since HTTP header). But since using 304 in the absence of If-Modified-Since is non-standard behavior, it's quite possible most calender applications aren't going to handle it.