Connectors for Lightning/Sunbird: Difference between revisions

(More details, how WCAP would be a solution.)
No edit summary
Line 1: Line 1:
As of Lightning/Sunbird version 0.3, there is definitely read/write support for WCAP (Sun ONE's XML/RPC calendar protocol).  If Zimbra exported a WCAP interface, which appears to be quite a simple protocol,
As of Lightning/Sunbird version 0.3, there are three supported remote calendar protocols:
many people would be able to replace Outlook with entirely free software.  Maybe this is not strategic for Zimbra.com, as the Outlook connector is one of the major reasons to buy the Network Edition.


michael-fig writes:
1. WCAP (Sun ONE's XML/RPC calendar protocol), which appears not to be documented anywhere, but can be reverse-engineered from Sunbird's mozilla/calendar/providers/wcap sources.  It looks like it just depends on plain-old GET and POST requests.
I am struggling to understand Tomcat (the last time I touched Java was before Swing was invented), but if somebody out there can help me understand how to modify Zimbra, I can reverse-engineer the protocol between Sunbird (whose WCAP sources I've already found) and Zimbra enough to get calendaring working.
 
2. iCalendar, which uses the PUT method to send the complete updated calendar to the same Zimbra URL.  This could get very inefficient with large calendars, and then Zimbra would have to delete events from the calendar folder to make sure there aren't duplicates.  It also uses a PROPFIND, which is rejected by Tomcat.
 
3. CalDAV, which uses the REPORT method to get a listing of calendar entries, and PUT to update them (neither of which are supported by Tomcat).
 
I'd suggest that CalDAV is going to be the best in the long run, but with today's technology, WCAP will be easiest to support.  Does somebody out there have a pointer to WCAP's specification, to avoid having to reverse-engineer things?

Revision as of 05:30, 20 October 2006

As of Lightning/Sunbird version 0.3, there are three supported remote calendar protocols:

1. WCAP (Sun ONE's XML/RPC calendar protocol), which appears not to be documented anywhere, but can be reverse-engineered from Sunbird's mozilla/calendar/providers/wcap sources. It looks like it just depends on plain-old GET and POST requests.

2. iCalendar, which uses the PUT method to send the complete updated calendar to the same Zimbra URL. This could get very inefficient with large calendars, and then Zimbra would have to delete events from the calendar folder to make sure there aren't duplicates. It also uses a PROPFIND, which is rejected by Tomcat.

3. CalDAV, which uses the REPORT method to get a listing of calendar entries, and PUT to update them (neither of which are supported by Tomcat).

I'd suggest that CalDAV is going to be the best in the long run, but with today's technology, WCAP will be easiest to support. Does somebody out there have a pointer to WCAP's specification, to avoid having to reverse-engineer things?

Jump to: navigation, search