Hello
I found the spec intentionally omits "server-alerted slow sync". What is the
reason for that?
Because of this, I have to manually wiping the stored anchor at server side to
trick the client to carry a slow sync. Is there some easier way to do this?
--
Regards,
Chen Congwu
Moblin China Dev
Hello Chen
slow syncs should be omitted anyway whenever
possible, as they create a lot of traffic and
have the inherent problem of duplicates. The
server can still force a slow sync in the session
initated by the SAN, and it will do that if
really requested on server side.
So yes, you can
Hi Patrick,
On Nov 25, 2009, at 8:38 , Patrick Ohly wrote:
> [...] we now instantiate one engine for logging,
> destruct it, then construct the final engine.
>
> The resulting log is okay, but not perfect. It contains the
> "Start of log - Synthesis SyncML Engine 3.3.0.0" preamble
> twice. The
Hello Congwu,
On Nov 25, 2009, at 2:19 , Chen Congwu wrote:
> While I was enabling superdatastore for SyncEvolution server usage, I found
> the
> config file "syncserv_sample_config.xml" needs some minor fixing:
>
> It was using a bool variable 'ISEVENT' to differeciate events and todos, while
Hello,
On Nov 24, 2009, at 16:50 , Yiping Cheng wrote:
>Thank you so much for your great help! Your guess is completely correct
> and I have
> now fixed the problem by adding initialization code in the main program.
Thanks for the feedback, glad I could help :-)
>Now there is another p
