In a SymmetricDS network topology where a server is configured to pull data from thousands of clients, the latency can become greater than desired due to the network overhead of having to connect to a client to see if it has data to pull.

The reason a pull configuration like this might be used (versus the more efficient push configuration) is so the overall network bandwidth usage can be controlled from a central location.

The design allows for the pull configuration, but also includes enhancements for SymmetricDS clients to report their outgoing batch status so that nodes that have data can be prioritized for pulling. The design does require the ability to create an HTTP connection from both the server and the client.