My application generates a high enough number of records in a single table to send to the RhoConnect server.
Synchronization runs automatically in the background using a 600 second sync_poll_interval.
If the sending of the data from the client to the RhoConnect server is interrupted before its completion, in the next synchronization this information is sent again together with the new generated, and so on.
When the volume of the data grows, the possibilities that the communication does not come to an end also grow, creating a traffic jam that is almost impossible to solve.
Would there be any way to paginate the upload traffic to the server, so that partial shipments are made easier to transmit?
The PageSize parameter is also used in the upload ?.
How can it be changed through the communication file or by program?
This problem does not occur in sending data from the server to the client, both in normal and bulk synchronization.
The problem occurs in the sending of information from the client to the server. In this case, if the sending of the records does not finish and the call to the 'query' method does not occur, the client does not give as transmitted these records and repeats their sending in the next synchronization.
I do not know if the problem occurs in communications or in queries to redis, since I do not have any tool to trace communications and the only information I get from calls to the methods of the models