Linked by Thom Holwerda on Tue 18th Dec 2012 00:03 UTC
Microsoft Microsoft has just responded to Google's move regarding Exchange ActiveSync. Sadly, instead of addressing the very real problems consumers are about to face, Microsoft starts talking about switching to Outlook.com.
Thread beginning with comment 545609
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Switching
by chithanh on Tue 18th Dec 2012 08:13 UTC in reply to "RE[3]: Switching"
chithanh
Member since:
2006-06-18

If you equate "public" with "open", then you may be correct.

I however like to think that "open" means that anybody can participate in the process of developing the protocol. This is not the case here, the protocol is decreed by Google.

Secrecy, fees (e.g. due to patent encumbrance) and such are sufficient conditions for being proprietary, but not necessary.

Reply Parent Score: 2

RE[5]: Switching
by Vanders on Tue 18th Dec 2012 10:40 in reply to "RE[4]: Switching"
Vanders Member since:
2005-07-06

I however like to think that "open" means that anybody can participate in the process of developing the protocol. This is not the case here, the protocol is decreed by Google.

No it isn't. It's IMAP. Google's extensions are defined by Google, but you're welcome to implement your own version of those extensions, or totally different extensions. You're also welcome to write an RFC based on those extension and submit it to the IETF, at which point they'd become "standard".

Reply Parent Score: 7

RE[6]: Switching
by chithanh on Wed 19th Dec 2012 18:03 in reply to "RE[5]: Switching"
chithanh Member since:
2006-06-18

No it isn't. It's IMAP. Google's extensions are defined by Google, but you're welcome to implement your own version of those extensions, or totally different extensions. You're also welcome to write an RFC based on those extension and submit it to the IETF, at which point they'd become "standard".

I understand and don't dispute that. But in contrast to IMAP which is standardized by the IETF, nobody prevents Google to change their non-standard extensions in an incompatible way tomorrow, rendering your implementation useless. No process is in place that enables participation.

Reply Parent Score: 1