First some upgrades has been done to the SyncML interface:
- It is now possible to synchronize the calendar! This wasn’t difficult to implement but as many phones have very limited capabilities for managing events, it had been put aside for a while.
- There are aliases for databases (i.e: card can be used instead of contacts), this should reduce the chances of wrongly configuring a device and improve compatibility with Funambol clients who assume different database names by default.
Following this, small improvements have been done on the Web interface. It is now possible to import recurrent events will with older vCalendar 1.0 files (previously only iCalendar 2.0 was supported). A bunch of minor bugs have been corrected as well.

When will it support syncing external calendars as well? Right now I have subscribed to 4 calendars and would like to have them pushed to my mobile. That’s the single major feature for me
Thanks!
Igor
Comment by Igor — October 19, 2009 @ 9:32 pm
Thanks for the suggestion – I’ll add it to the list of features to add, this should definitely be doable.
Comment by Pierre — October 20, 2009 @ 3:04 am
Thanks for your great SyncML service!
BTW. Do you support both iCal 2.0 and vCalendar 1.0 for calendar synchronization?
Comment by dh — January 13, 2010 @ 5:53 am
Almost – it will understand iCal 2.0 from the phone (in fact the decoder can handle any sort of “soup” of vCal 1.0 and iCal 2.0 encoding) and can output to iCal 2.0 as well, but it lacks the ability to detect the client’s format preference. So right now it will always default to sending its own data in vCalendar 1.0 (but will not complain about receiving iCal 2.0, so one way sync or refresh from client will work in 2.0).
As all clients I’ve seen so far work with 1.0 this isn’t really a high priority improvement, but if there’s a need it won’t take too long to implement. (similarly this would allow vCard 3.0 as the encoders and decoders are already implemented)
Comment by Pierre — January 13, 2010 @ 7:20 am