In that case, how does Zimbra iSync work with 10.4 Tiger?
Case a) It uses SOAP — but they completely disable that if you're on Leopard.
Case b) It uses CalDAV (or WebDAV?) as the transport but doesn't create a CalDAV account in iCal 2 (obviously). And again this is completely disabled when you have CalDAV 3....?
I may be mistaken but I think that whatever method is used in Tiger is still available in Leopard. My reason for believing this is that there are a number of messages on the forum from people who, on switching to iCal 3/CalDAV, still have their iSync going, resulting in duplicated calendars.
Last edited by ewilen; 02-10-2009 at 01:41 PM..
|