You can't just quickly rewrite it, either. You can't put DavMail into Thunderbird, because it's all written Java. I don't see why the functionality can't be put directly into tb You're essentially making "bug for bug compatibility". But if you do in the straight-forward way, it breaks badly for some users. You run into all kinds of edge cases that nobody ever defined and make no sense whatsoever and just happen to work with MS Outlook. The mess that this creates becomes very clear when you try to implement it and get it to production quality where it really works for end users in practice, not just a tech demo. For Microsoft, if MS Outlook works and their website works, it's fine. They don't even adhere to their own (!) protocols which they themselves made up, and they can't even adhere to that. Microsoft doesn't believe in the concept of standards. Every few years, they invent a new one, which is then the "right" one. Exchange speaks at least 8 different (!) protocols for getting mail, and EWS is just one of them. You cannot pick which one to implement and use, because the admins often disable many of them. EWS is specifically for Exchange and Office365.Īnd not even all servers and Office365 domains have EWS enabled, either, so you need to implement even more protocols. Sounds like EWS must be a non-proprietary protocol.Įven though it's documented, EWS is very much a proprietary protocol.
0 kommentar(er)
