Hi, No Ray, it is not related to that.
I've some updates to this. How to reproduce: 1. Delete main calendar from Calendar UI 2. Full synchronize some stuff in (not sure is this really necessary) 3. Request: www.google.com/calendar/feeds/default/private/full?updated-min=2009-07-31 -> DEFECT: Response: Error 410: "Gone" It is required that updated-min date AND calendar deletion date are the same. As it is stated in change log that: "Ensure that HTTP 410 (Gone) is returned if `updated-min` is set to a date before the last time a calendar was cleaned. This allows sync clients to know that all events are out out of sync and that a complete rebuild should be performed. (Requires protocol version 2.1.) " I guess you guys are comparing (updated-min <= cleanDate) where you should compare (updated-min < cleanDate) as today with same test account following request succeeds: www.google.com/calendar/feeds/default/private/full?updated-min=2009-08-01 BR, Petteri On Jul 31, 9:31 pm, Ray Baxter <[email protected]> wrote: > I think that your answer is on that page. > "Please keep in mind that it may take a few moments to fully access Google > Calendar's features after clearing your primary calendar." > > That's the English for 410 Gone. > > Ray > > > > On Fri, Jul 31, 2009 at 11:23 AM, petteri <[email protected]> wrote: > > > Oh sorry I wasn't clear enough. Please refer to Google Calendar Help > > how to delete a calendar, there is also an explanation what happens to > > primary calendar. > > >http://www.google.com/support/calendar/bin/answer.py?hl=en&answer=37188 > > > On Jul 31, 9:14 pm, Ray Baxter <[email protected]> wrote: > > > You need to clarify exactly what you are doing when you "delete main > > > calendar". > > > Are you saying that you obtain a list of all of the events on that > > calendar > > > and individually delete each of them? Or are you doing some operation on > > the > > > client side, syncing that to Google, and then receiving the 410? What is > > > that operation? How are you syncing? > > > > Ray > > > > On Fri, Jul 31, 2009 at 10:56 AM, petteri <[email protected]> wrote: > > > > > Ehm you lost me. Deleting default/main calendar on Google calendar is > > > > more like emptying it. Those were an instructions how to reproduce a > > > > behavior I think is a defect. > > > > > On Jul 31, 7:48 pm, Ray Baxter <[email protected]> wrote: > > > > > You are deleting a resource and then requesting it. A response code > > of > > > > 410 > > > > > Gone make senses to me. > > > > > What am I missing, other than the secret to how or why you are > > deleting > > > > > your main calendar? > > > > > > Ray > > > > > > On Fri, Jul 31, 2009 at 7:03 AM, petteri <[email protected]> wrote: > > > > > > > Hi, > > > > > > > I'm now able to reproduce this problem. Here are the instructions: > > > > > > > 1. Delete main calendar > > > > > > 2. Full synchronize some stuff in (not sure is this really > > necessary) > > > > > > 3. Request: > > >https://www.google.com/calendar/feeds/default/private/full?updated-mi.. > > > > .. > > > > > > .. > > > > > > -> DEFECT: Response: Error 410: "Gone" > > > > > > > Note, today is 2009-07-31. > > > > > > > BR, > > > > > > Petteri > > > > > > GoogaSync.com > > > > > > > On Jul 31, 4:43 pm, petteri <[email protected]> wrote: > > > > > > > I'm also defining that use GData-Version 2.1, why these changes > > are > > > > > > > affecting to my users? > > > > > > > > On Jul 31, 4:40 pm, petteri <[email protected]> wrote: > > > > > > > > > Hi, > > > > > > > > > I am getting reports from my users that they are getting 410 > > GONE > > > > even > > > > > > > > though updated-min date is set properly? Can you elaborate more > > > > what > > > > > > > > is actually changed? > > > > > > > > > BR, > > > > > > > > Petteri > > > > > > > > GoogaSync.com > > > > > > > > > On Jul 30, 8:12 pm, Trevor Johns <[email protected]> wrote: > > > > > > > > > > Hello everybody, > > > > > > > > > We have a new Calendar Data API release for you all. The > > > > changelog is > > > > > > > > > below. > > > > > > > > > > As always, you can subscribe to the Atom feed athttp:// > > > > > > code.google.com/apis/calendar/changelog.htmltogetthe latest > > > > > > > > > news on > > > > > > > > > any future releases. > > > > > > > > > > Calendar Data API Release 2009-08 > > > > > > > > > Date: July 29, 2009 > > > > > > > > > Description: > > > > > > > > > > This release fixes the following issues: > > > > > > > > > > - Ensure that HTTP 410 (Gone) is returned if `updated-min` is > > set > > > > to > > > > > > a > > > > > > > > > date > > > > > > > > > before the last time a calendar was cleaned. This allows > > sync > > > > > > > > > clients to > > > > > > > > > know that all events are out out of sync and that a > > complete > > > > > > rebuild > > > > > > > > > should > > > > > > > > > be performed. (Requires protocol version 2.1.) > > > > > > > > > - If both `gd:when` and `gd:recurrence` data are specified > > when > > > > > > > > > creating an > > > > > > > > > event entry, an HTTP 400 (Bad Request) error is returned. > > > > > > > > > - Issue 866: Attempting to configure a calendar to use an > > invalid > > > > > > > > > timezone now > > > > > > > > > returns an HTTP 400 (Bad Request) error rather than > > defaulting > > > > to > > > > > > > > > UTC. > > > > > > > > > > -- > > > > > > > > > Trevor Johns --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
