[sync] sync happens only one way, Mimetype mismatch for server-to-client data

Fri Oct 6 04:03:28 PDT 2006

Hi Karsten,

I'll be out of the office for the rest of the day, I'll try and provide them
on Monday at the latest. I'll use the horde test-case as defined in the Wiki
to generate the files.

Regards,
Jochem

-----Oorspronkelijk bericht-----
Van: Karsten Fourmont [mailto:fourmont at gmx.de] 
Verzonden: donderdag 5 oktober 2006 18:13
Aan: jochem at mondrian-it.nl
CC: sync at lists.horde.org
Onderwerp: Re: [sync] sync happens only one way, Mimetype mismatch for
server-to-client data

Hi Jochem,

can you send me the /tmp/sync/*.xml logs of such a session?
(Please start with a clean /tmp/sync/. You may also want to use a dummy 
password as it's in the logs.)

Thanks,
  Karsten

Jochem Meyers wrote:
> Hi all,
> 
> When synchronizing with Funambol WM 3.0.31, synchronization only occurs
from
> client to server, not from server to client. I followed the standard sync
> test protocol (as it's described in the wiki), with one item on the client
> (client1) and one on the server (server1).
> 
> The Client1 item shows up in Nag, but even after a complete resync, the
> server item does not show up on the client. The Funambol client does not
> appear to report an error.
> 
> I suspect this has something to do with the following. /tmp/sync/log.txt
> shows 
> 
> input received from client (text/x-s4j-sift)
> 
> for received data, but for outgoing data it says
> 
> converted for sync4j client: sif/task
> 
> The data after the client-to-server entry looks very much encoded. The
data
> after the server-to-client entry is plain xml:
> <?xml
>
version="1.0"?><task><Complete>False</Complete><DueDate>45001231T230000Z</Du
>
eDate><Subject>Server1</Subject><Body></Body><Importance>1</Importance></tas
> k>
> 
> I've tested this on two clients, with the same effect.
> 
> Regards,
> 
> Jochem Meijers
> Mondrian B.V.
> 