Linked by Thom Holwerda on Fri 14th Dec 2012 22:37 UTC
Google "Google Sync was designed to allow access to Google Mail, Calendar and Contacts via the Microsoft Exchange ActiveSync protocol. With the recent launch of CardDAV, Google now offers similar access via IMAP, CalDAV and CardDAV, making it possible to build a seamless sync experience using open protocols. Starting January 30, 2013, consumers won't be able to set up new devices using Google Sync; however, existing Google Sync connections will continue to function." Others are free to implement the open protocols.
Thread beginning with comment 545305
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: well good to hear
by Bill Shooter of Bul on Sat 15th Dec 2012 15:49 UTC in reply to "RE[4]: well good to hear"
Bill Shooter of Bul
Member since:
2006-07-14

"Advanced Features" == "working with Microsoft backend" ??

From a pragmatic view, I guess that would make sense to most non tech people. But to me, its more like Apple announcing that it wouldn't allow flash on its mobile devices. Its actually a good thing that will over time consign poorer, less open technology to the dust bin ( even though I didn't see that at the time). And in this case, most clueless consumers are going to blame Microsoft for not working with gmail and google calandar, rather than the other way around. They'll push microsoft to adapt to the open standards. That's pretty cool, in my book.


Microsoft is stuck though because they can't make money off of using open standards they could of implemented those a long time ago if they could.


No, I think they developed exchange at a time where other companies were doing their own proprietary email/calendaring solution ( ie lotus notes) . When the standards were developed, they already had a vast majority of the market and figured that they probably wouldn't make more money by opening up by choice. Now they are in a different competitive landscape where their users are going to demand that their clients support an open standard. If I were Microsoft, I wouldn't change Exchange, by any means, but change the clients on Windows phone 8 to integrate with Imap /caldav.

Reply Parent Score: 4

RE[6]: well good to hear
by Bill Shooter of Bul on Sat 15th Dec 2012 16:21 in reply to "RE[5]: well good to hear"
Bill Shooter of Bul Member since:
2006-07-14

Found this after I posted:

http://www.engadget.com/2012/12/14/editorial-windows-phone-future-w...

Microsoft *needs* to make its os work well with google products in order to have a chance. Again, If Google stops supporting a MS protocol in favor of an open one, MS needs to adopt the open one to keep customers happy.

Reply Parent Score: 4

RE[6]: well good to hear
by Windows Sucks on Sat 15th Dec 2012 18:27 in reply to "RE[5]: well good to hear"
Windows Sucks Member since:
2005-11-10

From a pragmatic view, I guess that would make sense to most non tech people. But to me, its more like Apple announcing that it wouldn't allow flash on its mobile devices. Its actually a good thing that will over time consign poorer, less open technology to the dust bin ( even though I didn't see that at the time). And in this case, most clueless consumers are going to blame Microsoft for not working with gmail and google calandar, rather than the other way around. They'll push microsoft to adapt to the open standards. That's pretty cool, in my book.


I actually work with Google Apps and did a 3000 seat implementation for the US government. Google is not going to get rid of Active Sync for their business clients. Users love using Outlook, iPhones and Blackberry's (BES uses Active Sync to connect to Exchange and also to Google Apps) Plus Windows 8 phones and even Android have the Active Sync client.

No, I think they developed exchange at a time where other companies were doing their own proprietary email/calendaring solution ( ie lotus notes) . When the standards were developed, they already had a vast majority of the market and figured that they probably wouldn't make more money by opening up by choice. Now they are in a different competitive landscape where their users are going to demand that their clients support an open standard. If I were Microsoft, I wouldn't change Exchange, by any means, but change the clients on Windows phone 8 to integrate with Imap /caldav.


You know that Microsoft sells their active sync implementation and make millions of just that alone??

And you also noticed that this coincides with Google getting rid of their free offerings of Google Apps right?

Microsoft is not going to change something they are making millions off of, Google is taking it out of their free offerings of Google mail only, the client will be in Android still and every other mobile OS still has it and it will stay in their business offerings that people pay for (To cover the license fees they pay Microsoft)

Reply Parent Score: 3

RE[6]: well good to hear
by pgeorgi on Sun 16th Dec 2012 11:53 in reply to "RE[5]: well good to hear"
pgeorgi Member since:
2010-02-18

They'll push microsoft to adapt to the open standards. That's pretty cool, in my book.

My guess is that they'll do it like the XMPP support in Messenger: Use the standard and a white list of peers.

So they'll only do caldav with Google (and maybe IBM/Lotus, Apple and RIM, if they follow Google's lead), but since every server and client that interacts with them would require some "API key" or white list entry, it remains a big boys' club - and that's something they can live with.

The real panic starts when they're forced to go openly federated - Google had their share of anxiety in that regard as well (Google Talk's XMPP was locked down for a long time, too).

Reply Parent Score: 3

RE[7]: well good to hear
by zima on Fri 21st Dec 2012 19:15 in reply to "RE[6]: well good to hear"
zima Member since:
2005-07-06

(Google Talk's XMPP was locked down for a long time, too).

Not really "a long time" - checking out http://en.wikipedia.org/wiki/Gtalk#History it was less than half a year, only some time. ;p

Reply Parent Score: 2