aboutsummaryrefslogtreecommitdiff
path: root/lib/connection.h
diff options
context:
space:
mode:
authorKitsune Ral <Kitsune-Ral@users.sf.net>2020-06-12 20:29:46 +0200
committerKitsune Ral <Kitsune-Ral@users.sf.net>2020-06-12 20:29:46 +0200
commitb1071cf34b86685c3cdb5004d6112881966a7ce6 (patch)
treedb55bfb3a906ef6152bcfa61aef16a3a09e6e911 /lib/connection.h
parentebdb2ba9d15e6cdfb1458e7895032afd641aafe3 (diff)
downloadlibquotient-b1071cf34b86685c3cdb5004d6112881966a7ce6.tar.gz
libquotient-b1071cf34b86685c3cdb5004d6112881966a7ce6.zip
Connection::syncLoop: give a pause between syncs
As it's observed now, Synapse responds almost immediately on /sync requests - even if there are no events to return. This downgrades long-polling to simply polling, and since clients don't expect it, polling loops become pretty violent. To alleviate that somehow, syncLoop now accepts the second parameter, msecBetween (500 msecs by default), to configure waiting between the previous sync response and the next sync request. This is only for syncLoop(); Connection::sync() fires instantly, as before.
Diffstat (limited to 'lib/connection.h')
-rw-r--r--lib/connection.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/connection.h b/lib/connection.h
index d5fa9eac..fb76cf3d 100644
--- a/lib/connection.h
+++ b/lib/connection.h
@@ -544,7 +544,7 @@ public slots:
void logout();
void sync(int timeout = -1);
- void syncLoop(int timeout = -1);
+ void syncLoop(int timeout = -1, int msecBetween = 500);
void stopSync();
QString nextBatchToken() const;