Add configurable cap on amount of data changeserver will send to a single client

[kriswehner]

What we've found in the past is there is a threshold of change size beyond which it actually makes more sense for the client to simply request a new snapshot rather than process that volume of change.

We would need a command line switch (default disabled?) that specifies the total amount of change a given client can handle, and if the client has more than this pending number of changes when they go to fetch data, the server should return a failure condition to them and instruct them to refresh their database.

[kriswehner]

Just to be clear: This isn't for a single response, but is the total number of pending changes for the client on the changeserver.