Bug 52809 - make timeout for first message in server initiated sync configurable
Summary: make timeout for first message in server initiated sync configurable
Status: RESOLVED MOVED
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: SyncEvolution (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: SyncEvolution Community
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-01 02:03 UTC by SyncEvolution Community
Modified: 2018-10-13 12:43 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Patrick Ohly 2012-07-29 18:36:00 UTC


---- Reported by congwu.chen@intel.com 2010-04-01 02:03:29 +0000 ----

The timeout used in SyncEvolution currently is:
server:
RetryDuration :timeout value
RetryInterval : no effect

client:
RetryDuration: client side resend give up time
RetryInterval: client side timeout value

The server side timeout was set as RetryDuration which is much longer than client side timeout because server side might have long-standing operations.

However this long timeout does not work for the first message in server alerted sync. So we need to better introduce two timeouts for server side:
1) a shorter timeout for sending the first message (when it is server alerted sync)
2) a longer timeout for sending later responses to client.



--- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC  ---

This bug was previously known as _bug_ 401 at https://bugs.meego.com/show_bug.cgi?id=401
Comment 1 GitLab Migration User 2018-10-13 12:43:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/102.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.