Problem

Confluence using Collaborative Editing does not offer the possibility/granularity to customize the web socket integration for Synchrony. Most of the Web Socket network-related timeout and settings configurations are hardcoded.

Suggested Solution

Make it possible to overwrite the default/recommended Web Socket integration for Synchrony.

Why This Is Important

In a heavily scaled instance, being able to tune the web socket could save a lot of calls back to Confluence and without significantly impacting a users experience.

Workaround

It is possible to force the connection to go through Web Socket for Synchrony you can disable the fallback XHR system by setting the system property -Dsynchrony.enable.xhr.fallback=false for the Confluence JVM and you won't be able to publish or save a page changes without a WebSocket connection.
In practice, this will constantly retry until the client can get a websocket connection so it can be impractical if the websocket connectivity is not reliable