[sync] Funambol 6.0.13 sync failed with Horde SyncML module

[Karsten Fourmont]

Hi,

I tried the funambol outlook connector 6.0.9 beta with Horde.

It seems the trouble comes from the gzip compression: The connector asks 
for it and so Horde delivers it. But the connector seems to choke on the 
compressed data.

The funambol logs produce something like:

14:51:45 GMT +1:00 [DEBUG] - Reading response...
14:51:45 GMT +1:00 [DEBUG] - Content-length: 533
14:51:45 GMT +1:00 [DEBUG] - Receiving data of size 533...
14:51:45 GMT +1:00 [DEBUG] - Finished receiving data of size 533.
14:51:45 GMT +1:00 [DEBUG] - Response read:
xœ¤T[oÚ0þ+(¯qÌ­´r\uclLÐMúî&²&q»úëçk".Y+•|rÎw.ßç“ ûCžuö´â)+Bú×¡EÌ’´Ø†Þz5펽{Œ¢c/æ‰-xèqù”gwæ€>ôàgRaôD«Éj‚¥
k+ߟŠ 
†Mà‚Ɖ"ÊU÷™Ì‚7ãÁpxh¼hÁ·*ˆ€1ЊT[*0š³x½œá
˺Ñ÷§_«—õˆô¦Ç¸¿Ìž·aˆ€(à#É)”5µŽh®XÄ^«˜ÖEwB”w

As a workaround you can turn of the gzip compression in the horde setup:

$conf['compress_pages'] = false; (in horde/conf.php)

This seems to be a bug in the Funambol connector.

But I found a glitch in Horde as well: I tried to create a "Browser 
Quirk" so that
if $browser->hasQuirk('buggy_compression') returns true in Horde.php.
But the function Horde::allowOutputCompression() seems to be never 
invoked! Do we need to invoke it in Horde::compressOutput()?

Cheers,
  Karsten



Jochem Meyers wrote:
> Hi all,
> 
> I've been trying out the funambol 6.0.13 (the new beta) for windows mobile,
> syncing it against horde's syncml backend. 
> 
> The PDA is set up to synchronize server-to-phone only. Horde's logs indicate
> that the PDA requests a sync with anchor 0, and says it's initiating a
> slowsync (as is to be expected).
> 
> After a few seconds, the pda comes back with the warning that the sync was
> not completed. The logs say the server returned exit code -1.
> 
> Syncing with the latest 3.x version of the plugin works as it should.
> 
> Regards,
> 
> Jochem Meijers
> 
> P.s.: I've x-posted this to both the funambol-user list and horde's sync
> list, as I know there's plenty of people on both that use this combination,
> and might have some more insight into the cause and a potential solution. If
> the solution lies in Horde's implementation, please let me know, I can
> attempt to supply a patch.
>