You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just wondering, in the F-Droid variant, for background sync we are passing (by default) an HTTP long-polling timeout value of 6 seconds (&timeout=6000) to the homeserver. Why? What exactly is the purpose of waiting for 6 seconds? It doesn't seem to make any sense.
Why not just have the timeout be 0? (i.e. return request immediately, and then poll again after the configured delay amount, rinse and repeat).
This discussion was converted from issue #2017 on August 28, 2023 09:13.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was just wondering, in the F-Droid variant, for background sync we are passing (by default) an HTTP long-polling timeout value of 6 seconds (
&timeout=6000) to the homeserver. Why? What exactly is the purpose of waiting for 6 seconds? It doesn't seem to make any sense.Why not just have the timeout be 0? (i.e. return request immediately, and then poll again after the configured delay amount, rinse and repeat).
Beta Was this translation helpful? Give feedback.
All reactions