Hello Luz, I come up with this simple fix, I just add a flag to help. For synthesis server, next sync can still resume even if client failed to send an suspend alert; while this maybe not true for other servers. Scheduleworld is such a server.
>-----Original Message----- >From: [email protected] >[mailto:[email protected]] On Behalf Of Chen, Congwu >Sent: Wednesday, June 24, 2009 2:15 PM >To: [email protected] >Cc: [email protected] >Subject: Re: [os-libsynthesis] Synthesis client sometimes does not send an >suspend alert during suspending > >Hello Lukas, > Do you have any points on this? Based on my understanding synthesis lib >will append the suspend alert while it is sending out a message. After >receiving >the response, it will abort directly because it thought the alert was already >sent. > However if the client suspend just after sending a request and before >receiving >the response, synthesis lib will not send a suspend alert! > >>While I am working on suspend/resume support for SyncEvolution, I found >>synthesis client sometimes doesn't send a suspend alert. Details is: >> >>ces_generating -> ces_dataready -> ces_needdata -> ces_processing >> >>If the client suspends the session after generating but before dataready state >>(I did this during one step after StartDataRead), during processing, the >>client >>will abort without sending an alert(see SyncClient::MessageStarted, while >the >>comment asserts an alert should have been sent in the previous message). >> >>Is this behaviour as expected? > >-- >Regards > >_______________________________________________ >os-libsynthesis mailing list >[email protected] >http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
0001-Suspend-ALERT-make-sure-synthesis-client-sends-the.patch
Description: 0001-Suspend-ALERT-make-sure-synthesis-client-sends-the.patch
_______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
