http://bugzilla.moblin.org/show_bug.cgi?id=3427 pohly <patrick.ohly(a)intel.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick.ohly(a)intel.com --- Comment #11 from pohly <patrick.ohly(a)intel.com&gt; 2009-07-21 03:01:38 --- (In reply to comment #10) Is this logic inside the specific transport (CurlTransportAgent/SoupTransportAgent) or at some higher protocol level? I think it should be at some higher level, for example the main EvolutionSyncClient event loop. Because TransportAgent::send() is allowed to block (curl), some kind of idle callback would be needed to implement this approach. It would have the advantage that it only needs to be implemented once and has better access to context information (timeout settings in configuration, information about peer) to make policy decisions and/or notify the user. We need to cover two error scenarios: * message reached the server, only its reply is lost => server must handle duplicate messages * message never reached the server Can't we test this with intercepting messages, like we do for the interrupt tests? -- 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.