Bug 52919 - CalDAV + Google: implement constant request rate
Summary: CalDAV + Google: implement constant request rate
Status: RESOLVED MOVED
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: CalDAV/CardDAV (show other bugs)
Version: unspecified
Hardware: All All
: high enhancement
Assignee: SyncEvolution Community
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-16 21:00 UTC by Patrick Ohly
Modified: 2018-10-13 12:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

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


---- Reported by patrick.ohly@intel.com 2011-06-16 21:00:19 +0000 ----

The Google calendar server starts sending 401 errors when too many requests are sent. The current code detects that and then retries the same request after increasing delays.

However, each new request is always sent immediately, and thus runs into the same 401 error, and so on.

We should remember across requests that delays were necessary and thus sent requests at a rate that the server considers acceptable, but not faster.

To reproduce the problem, try:
CLIENT_TEST_NUM_ITEMS=100 CLIENT_TEST_MODE=server CLIENT_TEST_SIMPLE_UID=1 CLIENT_TEST_UNIQUE_UID=1 CLIENT_TEST_SERVER=google-calendar CLIENT_TEST_EVOLUTION_PREFIX=file:///tmp/test_ ./client-test Client::Sync::eds_event::testManyItems



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

This bug was previously known as _bug_ 19432 at https://bugs.meego.com/show_bug.cgi?id=19432
Comment 1 GitLab Migration User 2018-10-13 12:41:40 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/70.


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.