Odd patterns on sync request

[juliusknorr]

Having just one browser window open for a longer time I've noticed that sync seems to run still way too often if nothing is happening:

Also there seems some way of double fetching still ongoing:

[max-nextcloud]

I think one part of the problem is that awareness messages are also creating steps now. So Polling backend acts as if someone was typing because steps came in and resets the refetch timer:

With a single user awareness messages are send once per 15 seconds. So the timer goes down to 300, then up to 600, 1200, 2400, 4800 and just when it reached 5k the next awareness step arrives and it starts at 300 again.

One way around this would be to check the message type. Another option might be to reset the refetch timer whenever the document changes - not when steps come in.

[juliusknorr]

Right, maybe we can already solve this when looking into #3732 if the awareness state is not a step anymore?

[max-nextcloud]

#3776 fixed this with respect to the awareness messages. They are now transported via the session data rather than the steps so the refetchTimer won't be reset anymore because of awareness messages.

If new odd patterns in sync show up please reopen this issue or file a new one.