Connectors for Lightning/Sunbird: Difference between revisions
Michael-fig (talk | contribs) No edit summary |
Michael-fig (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
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). | 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' | michael-fig writes: | ||
It looks like WCAP or CalDAV are the way to go. I'm going to look if it's possible to extend Tomcat to understand REPORT and PUT. If not, I'll try WCAP. | |||
Revision as of 05:50, 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 is implemented in Sunbird's mozilla/calendar/providers/wcap sources. It uses plain-old GET and POST commands, and its online specification is at Overview and Commands.
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).
michael-fig writes: It looks like WCAP or CalDAV are the way to go. I'm going to look if it's possible to extend Tomcat to understand REPORT and PUT. If not, I'll try WCAP.
