Google to allow Microsoft to continue to use CalDAV protocol

Google announced quite a few projects will be shutting down on their end in the next several months, and the CalDAV API will become one of those projects on September 16th for most developers. However, a few developers will be "whitelisted" and will be allowed to continue to use the CalDAV email protocol.

The good news for Windows Phone users is that Microsoft will be one of those developers on that whitelist, according to what Google told ZDNet.com today. You may remember that Microsoft is currently working to support both CalDAV and CardDAV protocols for a future version of Windows Phone that would allow those devices to connect directly to Google's Gmail accounts.

Google was going to cut off adding new Windows Phone devices via the Exchange Active Sync protocol at the end of January 2013 but at the last minute, Google extended that deadline to July 31st so that Microsoft could adapt Windows Phone for the CalDAV and CardDAV. EAS support was cut off for new Windows 8 and Windows RT PCs on January 31st as planned, although Microsoft did offer workarounds for users who still want to connect to their Gmail accounts.

Source: ZDNet.com | Image via Google

Report a problem with article
Previous Story

Apple updates Boot Camp to support Windows 8

Next Story

Bill Gates among celebrities affected by financial info posted on website

35 Comments

Commenting is disabled on this article.

Heh, Google dropping EAS support right after Microsoft launches a competing mobile product, which happens to be... relying on EAS. Real nice Google, real nice...

Open Standard is a double edge sword... While its good so that everyone can use it without having to deal with a potential law suite... Its also half baked crap at the same time... People can hate proprietary software, but at the end of the day it just works better...

Showan said,
Open Standard is a double edge sword... While its good so that everyone can use it without having to deal with a potential law suite... Its also half baked crap at the same time... People can hate proprietary software, but at the end of the day it just works better...

Open Source software isn't safe from law suites. A LOT of Open Source flat out violates software patents, but no one cares until a big company worth bringing to court gets involved.

I really used to be a HUGE google fan, love their products, but my god they are becoming retarded lately, i think their products have started to get worse and the fact that i had to put up with their **** customer service where they nearly stole £600+ from me, just ****ed me off big time and now ive pretty much moved all my stuff to microsoft (surface RT, outlook, skydrive etc) just cant seem to let go of youtube though,

anyone know a good alternative, i like watching vlogs (CTFxC, lockergnome, eat your kimchi etc)

mrlcutleruk83 said,
I really used to be a HUGE google fan [...]

Me too. And I was also a big fan of Microsoft and a few months ago I would say that I love Amazon. I've learned is that no corporation deserves my loyalty. I simply don't dislike them.

Lets get this fully in perspective so there are no mistakes. Google told everyone that EAS was outdated and used proprietary technology to sync mail and contacts and calendar. They then claimed that IMAP, CalDAV and CardDAV were the right way to sync mail and contacts and calendar. Several months later the ball is going to be dropped on anyone that is still using EAS with gmail, any new devices could the not be used with EAS.

Now they obviously planned this whole transition out. But cue up March 13th and they now announce CalDAV is being put out to pasture because Google Calendar API is apparently better. To even access CalDAV with googles mail system you have to be whitelisted - likely a near impossible task unless you are some huge fortune 500 company.

So just to be clear - proprietary standards like EAS are bad because Microsoft made them, CalDAV is a better solution because its open source but technically very inferior to EAS, but then months later Google Calendar API is now better because its proprietary and made by Google. Did I get that right?

Looks like a bunch of scumbag hypocrites are in charge at Google; in fact I'd suggest anyone that works at google has to be a scumbag to even put up with that nonsense. You know what happens when you keep dropping api support for your products? Developers just stop bothering to support your s*** because they know your products are not reliable. It's quite clear that the only way to access gmail is to use imap or google own website/app and that is what Google wants so you have to see their disgusting ads - all of which are poor alternatives to EAS.

There's actually a much better solution - simply drop your gmail account and move to outlook or any other RELIABLE EMAIL company. Google's gmail is NOT RELIABLE and the company DROPS PRODUCTS like Reader whenever they feel like it because they are hypocrites. What is really disgusting is they knew they had no intentions of ever supporting CalDAV because this decision was not made overnight - so during the entire period of saying EAS is proprietary they intended the entire time to replace it with Google Calendar API eventually anyway.

Setup a free email account at http://www.outlook.com
Go into your gmail account's options page and setup forward to forward all mail to your new outlook email address
Setup your new outlook email address in your phone/computer and get reliable email that is PUSHED to the device in real time.
Wash your hands of google and their adware ridden services that are half-a$$ed anyway.

wingliston said,
I don't need it anymore. Forwarding my Gmail to Outlook.
I did this after the EAS announcement. GMail just isn't in the same league as Outlook.com. In comparison GMail just feels a bit 1990's.

wingliston said,
I don't need it anymore. Forwarding my Gmail to Outlook.

I did this with my Yahoo email (I know, I know... sigh. But I have this email account for years and its of sentimental value!)

BajiRav said,
So where the open source hippies who claimed Google is doing the right thing by supporting CalDAV over EAS?

Give them some time to come up with a good excuse, not that there is one.

I have had it with Google, have been a real fan of them in the past, but they're really acting childish right lately.
First they blocked Google Maps, then they blocked YouTube (I was affected by both blocks), then they announce that you won't be able to properly sync Gmail anymore, now this... makes me wonder what is next!
But anyhow, it does not matter anymore here, I've moved to Outlook, had no issues so far. Too bad Google has a 96% market share here (but they don't have any competitors here... Bing is still the same here as Windows Live Search, or MSN Search for that matter).
Still glad I picked a Lumia 800 though!

The hypocrisy is amazing, absolutely amazing. Where are the folks that were claiming google were great for dropping EAS for open standards (which don't work as good as EAS anyway) now? Google will drop this and use proprietary protocols in the future, google really are becoming the most hated tech company for me...........FULL OF S**T!

Google is full of sh**.

Google said that it discontinued EAS for CalDAV and CardDAV, because they are open sourced.

Now it discontinue CalDAV in favor of its own proprietary standard.

Even though they've let Microsoft use the protocol, I can't believe the hypocrisy of this. Google said they were dropping EAS support because they'd rather developers use CalDAV and CardDAV, since they're open standards. Now they're dropping support for CalDAV in favour of their own proprietary standard!?

Meph said,
Even though they've let Microsoft use the protocol, I can't believe the hypocrisy of this. Google said they were dropping EAS support because they'd rather developers use CalDAV and CardDAV, since they're open standards. Now they're dropping support for CalDAV in favour of their own proprietary standard!?

Hey man, this was hard on Google, too. They had to shut down Reader just to have a big enough distraction so people wouldn't notice the CalDAV thing. They really suffered for that.

georgevella said,
Wait a second, they stopped EAS support and now they are stopping CalDAV too?

Yeah, so much for open standards and all that BS from them, it sounds like they'll drop CalDAV for their own in house option from what I heard.

georgevella said,
Wait a second, they stopped EAS support and now they are stopping CalDAV too?

When Google says "Proprietary solutions like EAS should be shelved in favor of open solutions like CalDAV",

Google means "We want to be the next EAS."

GP007 said,

Yeah, so much for open standards and all that BS from them, it sounds like they'll drop CalDAV for their own in house option from what I heard.

Yup.

"Most developers' use cases are handled well by Google Calendar API, which we recommend using instead."

GP007 said,

Yeah, so much for open standards and all that BS from them, it sounds like they'll drop CalDAV for their own in house option from what I heard.


better than Microsoft proprietary BS

ahoncbt said,

better than Microsoft proprietary BS

Why. Why is Google's proprietary technology better than Microsoft's standard that they gladly licensed for anyone to use against all sorts of use cases.

Or are you just a hater that doesn't know why he feels the way he feels?

ahoncbt said,

better than Microsoft proprietary BS

Wow. Microsoft actually licenses their standard out and you get FULL documentation of how it works and examples of how to use it unlike googles CLOSED standards which you get absolutely no internal information on.

ingramator said,

Wow. Microsoft actually licenses their standard out and you get FULL documentation of how it works and examples of how to use it unlike googles CLOSED standards which you get absolutely no internal information on.


for money, yes. first they beg to make a tech standard and finally they show their true color.

Joshie said,

When Google says "Proprietary solutions like EAS should be shelved in favor of open solutions like CalDAV",

Google means "We want to be the next EAS."

Time to shove this in the face of all the fools who were praising Google when it was first announced they would itch EAS.

When will people learn that Google, Microsoft, Apple, Samsung, Sony... all of those companies AREN'T THEIR FRIENDS. They are concerned with one thing and one thing only: the wealth of their shareholders.

ahoncbt said,

better than Microsoft proprietary BS

Google's Calendar can now be accessed mainly through their API. Same with Exchange (only through EAS). Both are proprietary. The difference is that there are millions of devices TODAY that support Microsoft's "BS" - that have Microsoft's "BS" built in and already usable. Android devices, iphones, old smartphones, blackberries, etc., all can access any service available through EAS irrespective of the provider. Google simple shot themselves in the foot by cutting support for EAS. Now all these devices need a Calendar app that makes use of the Calendar API to be able to access Google's Calendar services.

pmdci said,

When will people learn that Google, Microsoft, Apple, Samsung, Sony... all of those companies AREN'T THEIR FRIENDS. They are concerned with one thing and one thing only: the wealth of their shareholders.

That's not entirely fair. At some level, yes, members of the companies are prioritizing profit and returns. But at many levels of a company, there are people who are more concerned with doing great things because it's their reputations, connections, and resumes on the line. Every company has some number of people--even decision makers--who want to be part of something exciting and meaningful because it's what gets them to their own personal next level.

I just wanted to point that out, because people get too rapidly caught up in corporate hate-ons and forget these things.