So you want to *receive* updates continuously (whenever another user presses "save") but only *send* your updates when you press "save"?
That's not currently possible, but could be implemented I guess. You'd basically need to modify the state machine in
client.js. So the default state behaves more like AwaitingWithBuffer (which queues up a buffer of operations) rather than Synchronized (which sends new operations immediately) and then plumb in a mechanism to flush the buffer. It'll be a bit tricky and you'll have to deal with all the state transitions (such as the user pressing save and then pressing it again before the first save completes).
If you decide to give it a go and have questions, let me know.
-Michael