http://bugzilla.moblin.org/show_bug.cgi?id=3427
--- Comment #20 from pohly <[email protected]> 2009-08-28 07:28:09 --- (In reply to comment #19) > Well, the testing have exposed a server side strange behavior > (scheduleworld/funambol): > Client::Sync::*::Resend::testResendClientAdd > ------------------ > The normal message work flow > out1: init sync > in1: init sync > out2: client changes > in2: acknowledgment to client changes > out3: Alert 222, continue > in3: server side changes > ... > ------------------ In this scenario the server has seen message "out3", but its reply never reaches the client, right? > If out3 is resent, the server will never send server side changes but just > acknowledges to the Alert222. The client has no way but continue send Alert > 222, which will never end... I bet the Funambol and ScheduleWorld server don't notice that the Alert222 is a resend and therefore just send their standard reply instead of resending their changes. Does it work if some of the earlier or later messages are resent? Can you bring this up on the Funambol *developer* list? Stefano Maffulli encouraged us to use that list instead of the "general discussion" list. This is probably worth mentioning before jumping into a description of the problem. What can we do about this issue? Ideally the engine would detect that no progress is made and abort, but I am not sure how easy that is. If we cannot implement that, can we skip this problematic resend in our testing? Alternatively we have to disable the Resend tests completely for Funambol and ScheduleWorld. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
