A default sync provider is designed to run on every WordPress installation. Therefore it must not use constructs or infrastructure that is not universally available.

• It should be based on HTTP polling
• Given the isolation and lifecycle of PHP processes, updates must be stored centrally (in the WordPress database) in order to be shared among peers.
• Collaborative editing can involve syncing multiple CRDT documents. To limit the number of connections consumed by this provider, requests should be batched.
• To prevent unbounded linear growth, updates should be periodically compacted.
• To avoid excessive load on lower-resourced hosts, consider usage limits (e.g., a maximum of three connected collaborators).