Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Google ending CardDAV and CalDAV support?
- Thread starter jason2811
- Start date
- Sort by reaction score
I haven't heard of this.
Are you sure you're not thinking of Google ending Exchange support? Different animal.
Are you sure you're not thinking of Google ending Exchange support? Different animal.
from the blog:
"We remain committed to supporting open protocols like CalDAV. "
They're shutting down "CalDAV API" for developers.
The difference is that developers for applications have a different access point for caldav than end user devices accessing individual accounts.
Also, Google isn't ending caldav API support entirely. It's ending support for an experimental version, and tightening up access to a production version in September.
Just wanted to note that CalDAV and CardDAV have been more reliable for me, in my experience, than EAS.
Also, EAS had annoying limitations in how you could set up contacts. For example, you could only have one "work" number or one "mobile" number for someone. With CardDAV those restrictions are no longer there.
EAS sucks. I'm glad Google has moved away from it (and is likely no longer paying patent license fees to MS for it). I have other problems with Google but this is definitely not one of them!
Also, EAS had annoying limitations in how you could set up contacts. For example, you could only have one "work" number or one "mobile" number for someone. With CardDAV those restrictions are no longer there.
EAS sucks. I'm glad Google has moved away from it (and is likely no longer paying patent license fees to MS for it). I have other problems with Google but this is definitely not one of them!
FWIW, a lot of the limitations in Google's implementation of EAS are not due to EAS itself. Most of the those limitations were because Google configured them in. Whether it was intentional or not is anyone's guess, but the EAS implementation I use at work isn't nearly as limited as Google's was, and EAS certainly doesn't suck when the admins configure it in a non-sucky fashion.
So, yeah, Google is pretty much where the problem was, all along.