3 ms·
> My point was that Exchange is not compliant enough to be usable from a non-Outlook email client. Well, you kind of have a point there. I use Apple mail and
by jedberg 14y ago
> My point was that Exchange is not compliant enough to be usable from a non-Outlook email client.
Well, you kind of have a point there. I use Apple mail and iCal against our corporate Exchange, but when I have to schedule a meeting, I either have to log into the Windows terminal server or use the outlook web interface to do it reliably.
It would be nice if there were an RFC for calendaring protocols, even if that RFC was just codifying Exchange.
- mattmanser 14y agoThere is, isn't there? http://www.ietf.org/rfc/rfc2445.txt http://www.ietf.org/rfc/rfc2445.txt Google seems to attach an ics to all the cal events it sends out.
- saurik 14y agoThat is only a mechanism for encapsulating an event and giving it to someone else: it doesn't really help any of the actual use cases people have for the kinds of group calendar management that everyone is used to having from Exchange. The more related standard that could have done this is ICAP, but that spec never happened and died as a draft back in 1998, long enough ago that the acronym got reused in 2003 by RFC 3507 for something unrelated to calendar access. http://tools.ietf.org/html/draft-oleary-icap-04 http://tools.ietf.org/html/draft-oleary-icap-04 Right now, it seems like all of the effort is behind CalDAV (which is based on WebDAV), which actually has some published RFCs behind it (dating back through 2007) and multiple clients (including Apple's iCal and Google Calendar). http://en.wikipedia.org/wiki/CalDAV http://en.wikipedia.org/wiki/CalDAV
- mattmanser 14y agoI see, thanks for the info!