I did my first tries with the proprietary google-api and the python
client-library, so far it works good, so I have no pressure to change.
But, good to know from you, that you had problems, so I can make a cross
to try out CalDAV from google.
On 06/02/11 14:11, Charles wrote:
If you're going to use CalDAV, good luck. Google doesn't even come
close to following the RFC. Yahoo comes closest to following the RFC,
Google is hit and miss - mostly miss - and loads of frustration,
workarounds, and special cases.
Charles.
On Feb 5, 5:36 pm, aldana<[email protected]> wrote:
I want to write client and am a bit unsure whether to use the more RFC
standard CalDAV or the google-api. My guess is that google-calendar api is
more powerful because customized for google calendar itself (less
abstractions necessary, no need for "over-abstractions").
Anyway my purpose is to write a client only google calendar so being RFC
standard argument doesn't count for me. What are the pros/cons of feature
richness of CalDAV vs. google-calender api?
Thanks.
--
manuel aldana
[email protected]
software-engineering blog: http://www.aldana-online.de
--
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
