CardDav and CalDav connector

I always wondered, why there was no CalDav/CardDav synergy connector for webOS. CalDav is one of these web (or at least web-like) open standards that webOS usually uses.

Since some time webos-ports put some effort in creating a synergy connector for CardCav. The repository can be found here. The day I recognized that activity I got in touch with them and moved the connector forward quite a bit. Especially the CalDav part and that it is using the webOS Mojoservice-Sync-framework which takes away a lot of the pain doing a synergy connector was my idea and my work. Currently I am using the connector fine on my Veer and my wife’s Pre 3 for calendar and contact sync (contact only one way from server, calendar two way). I still have a private fork with more experimental version here.

The software sadly did not make its way yet into Preware or the App catalogue… you can apply as beta tester by contacting me ;-). I am still testing with my eGroupware server. Owncloud also seems to work fine, now. I did some rudimentary tests with Yahoo (calendar seems to be fine). Google Calendar is not yet working, though.

I think if webos ports gets this synergy connector into a stable release, open webos will solve one of it’s more pressing issues: That there are no synergy connectors delivered with it.

I must admit that I like the caldav connector that much, that I stopped using SyncML. Therefore that is bad news for all my SyncML using friends: further development of the SyncML connector is rather unlikely. SyncML support seems to be fading out in most server implementations, because CalDav is much easier to implement (actually it’s very similar to webdav and most is done by the webserver already…). A lot of the knowledge I gathered in writing the SyncML connector and quite some bits of the code did go into the CalDav connector. So I’m quite happy with the current situation. 🙂

Actually the most pressing issue in SyncML was the slow sync that did happen from time to time and liked to mess up my data a lot.

Maybe, if there are people that are really in need of the SyncML connector and can’t use anything else and are willing in testing (and risk loosing/messing up their data), I’ll reimplement the SyncML connector in the Mojoservice-Sync-framework also, which takes away some of the issues the SyncML connector always had. Till then it might benefit from some improvements in iCal/vCard parsing and generation. But nothing happened on this front, yet.

5 thoughts on “CardDav and CalDav connector

  1. Is it possible to get an installable package for my Veer? I am especially interested in the CardDav portion because I want to push my CardDav data from my Daylite contact server.


  2. Stumbled upon this post, as i was looking for a sync method from owncloud to my pre3.

    By this message i would like to apply as a beta-tester as your post suggest:).

    I’m curious, as two-way sync for calender, 1 way for contacts suits my needs!

  3. I will contact you, soon. I’m currently waiting for the maintainer of the carddav connector to approve some beta release testing.

    1. Me wants some too! 🙂 I am applying as beta-tester. We are currently implementing SOGo in our company and I wanted to use it in coop with my Pre3.

  4. Hi,

    Ok, I’m trying organize some tests now. Could the people that are willing to test the connector send me some information to

    I’d like to know:
    – what devices you are going to test on (and which version of webOS they run)
    – what server you want to test with
    – a rough estimate of how many contacts and calendar events you want to sync (I’m somewhere around 50 contacts and 100-150 calendar events. If you have a lot more, I suspect issues which we need to investigate then)
    – how good your webOS / Linux skills are. Are you comfortable with the on device command line? Did you ever use Impostah? Do you know anything about the on device database? => I don’t want to exclude anybody, but it would be good to have an idea about how detailed my explanations have to be. Please try to be honest here.

    Of course you will have to have Preware installed on your devices. Also you must have a good backup of your data. Don’t that easy. It never happened over here, but potentially this app can screw up all your contacts and calendar events. On device and server! I will support you in cleaning up your device, if anything goes wrong. But I can’t do anything about your server. So please, be careful here. Better, maybe, test first with some test account or server, if possible.

    Also please not that this would be quite early testing. So expect bugs and stuff not working as you expect. Also features are missing. So, what is working:
    – downsync of contacts (also from multiple addressbooks, if your server has something like that)
    – downsync of calendars and calendar events
    – periodic syncs

    Upsync will be disabled for security reasons for the time being. Also what is not working currently (I’ll try to fix that, but I don’t know if I can find time on the weekend) is to disable contacts or calendar… you can currently only have both or none (i.e. delete the account, not sure if disabling does anything sensible right now). Image sync for contacts might also be broken for some servers… in fact contacts and events might sync down wrong, i.e. be corrupted on device (only for this synergy connector). That is one of the important things we need to test with as much servers as possible. Also, of course, the general carddav and caldav communication needs to be tested against multiple servers.
    Also it happened that the service went into an endless loop dragging all the resources from your device, memory, CPU, power (i.e. battery) and also data. It runs pretty stable now in all environments I tested it in. But if your environment differs, it might be different.

    IMPORTANT: Make sure the Patch “Sync fix for stable upload” is NOT installed on your devices.

    I’ll be happy to hear from you. 🙂

    PS: People that did not write here are, of course, also allowed to drop me an e-mail with the above information and so on.

Leave a Reply

Your email address will not be published. Required fields are marked *