On 05/27/2011 12:08 PM, Laurent Emil wrote: > Hi all, > I am testing sync evolution client and i encounter some problems when > stopping it with signal kill. > The problem is that server which i am testing against force slow sync at > the next synchronization session. I tried to implement a signal catcher > (to signal term) and i used the method api syncDone > <http://www.google.com/search?hl=en&client=ubuntu&hs=3ot&channel=fs&sa=X&ei=WGjfTZDsFdDYsgbv2L3BBQ&ved=0CBQQBSgA&q=m_source+ListPtr-%3EsyncDone&spell=1&biw=1600&bih=640>.
Have to admit I can't totally you follow you here. Can you be more specific about what client you are using and how? > The fact is that synchronization is stopped cleanly but that didn't > solve the slow sync issue already mentioned. > I know that Syncml standard require slow sync after a session failure > but i want to know if is there a method we call from client to close > session before we stop synchronization so we prevent slow sync in the > next synchronization. > In other words, Is it possible to stop a synchronization session between > Syncevolution client and server without launching a slow sync in the > next session ? Yes it is, if the server supports Suspend/Resume. You can try suspending with the syncevolution commanline by pressing ctrl-C once (second press will abort the sync). If you know that the server you are using does support Suspend/Resume but things just don't seem to work, that would be a bug somewhere... Let us know, we can then start digging in the logs. - Jussi _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
