What you want to do is very difficult and I don't really have any help for you. You want to minimize the communications overhead while still doing a distributed database synchronization. I'm not sure the best way for you to do that.

Posted by Myrroddin on Tue, 18 Oct 2011 15:07:07

You do not need to worry about overhead, or spamming the addon channel with AceComm-3.0, nor do you have to worry about the quantity of data you are sending. AceComm-3.0 splits the data into chunks, sends them in intervals, and reassembles the data. Automatically, behind the scenes.

But one thing to note: if what you are sending is not a string, you will also need to use AceSerializer-3.0 to serialize the data BEFORE you send, and use AceSerialize-3.0 to deserialize AFTER you get the comm.

Check both AceComm-3.0 and AceSerializer-3.0 documentation for more information, as Mr Whitehead is correct; you are asking for something that is fairly complicated.