Re: Sync problem, Funambol 8.0.3/Horde 3.3.4/Blackberry 8330 4.5.0.77: Part 2
Nicholas Istre <[email protected]>
| Newsgroups | gmane.comp.horde.sync |
|---|---|
| Message-ID | <1257288055.9119.49.camel@kanae> |
On Sun, 2009-09-06 at 21:28 +0200, [email protected] wrote: > Zitat von Jan Schneider <[email protected]>: > > > Are they kidding? They made every SyncML server supporting their > > proprietary SIF formats because they didn't support the established > > standards - and now that everyone has implemented it, they dropped > > support for it? This got to be a bad joke. > > From the Developers Guide for Version 8 > > Note: starting from Funambol version 7.1, both the server and the > client will use vCard as preferred format; the server will still > accept the old format for backward compatibility. Since vCard and > vCalendar/iCalendar are widely used standards and they must be > supported anyway, starting from Funambol version 7.1 the SIF > representation will be smoothly phased out. > > > That would mean they still cope with SIF-Format. Or maybe "smoothly > phasedout" mean "drop support in the next release"?? > > Regards > > Andreas > > I'm sorry about replying to this topic so late, but I've been hitting this issue too, running Funambol 8.0.4/Horde 3.3.5/Blackberry 9630 4.7.1.30 Simulator. I'm guessing there are plans on updating Horde to respond with vcards to the Funambol client in Horde 3.3.x? As it is, I need to patch our Horde setup as the Funambol client crashes with a JVM Error on my Simulator if I try to connect to our Horde/Turba install and synchronize contacts. 8.0.4 client works just fine if I connect to my.funambol.com though. I guess I'll try to get Funambol 7.1 working for our clients; I seem to have a similar crash with Funambol 7.2.3. Did they just drop SIF support there too? If so, love their definition of "smoothly phased out"! Best Regards Nick Istre -- sync mailing list - Join the hunt: http://horde.org/bounties/#sync Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [email protected]