On Sun, Feb 15, 2009 at 12:13 AM, Rolsch <[email protected]> wrote: > > Thanks for the answer - I don't agree... > > As developer, I FIRST want to test the new API version, before > implementing it - even if it's just a minor update! > > In my opinion, the header "Gdata-Version: 2" SHOULD default to 2.0, > otherwise it COULD break existing code, as it happened in my tool > (incremental date field with dates older than 26 days)!
Roland, Omitting the minor version number has always meant "use the latest minor version available". I'm sorry that this wasn't documented as well as it perhaps should have been. Another way to look at this: - There is already a way to request version 2.0 behavior. Namely, explicitly specify "Gdata-Version: 2.0". - However, if we make "Gdata-Version: 2" default to v2.0, then there will be no way to request the latest version. Moving forward, my recommendation is to always include the minor version number when making requests in the future. This way you can precisely control what version of the API you're working with. > btw: I tried it with header "Gdata-Version: 2.0", too... same "bug" > with &updated-min= I'm not sure I understand what you mean here. Can you be more specific? -- 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 -~----------~----~----~----~------~----~------~--~---
