Thanks for your reply!
I have another question about how the Wave server resolves conflicting
deltas:
Let's say Client 1 submits the delta {"a": "1", "b": "1"}. On the same
time Client 2 submits the delta {"a": "2", "b": "2"}.
Is it possible that the resulting state could be {"a": "1", "b": "2"}
or {"a": "2", "b": "1"}?
Or is is for sure that the state is either {"a": "1", "b": "1"} or
{"a": "2", "b": "2"}?
On 18 Jan., 13:34, "pamela (Google Employee)" <[email protected]>
wrote:
> That's a good observation. I think I would agree with you. It should
> only be necessary to iterate through the -vote keys and count them up.
> I imagine the author does the aggregate state for simplicity. Since
> he does keep all the state, he could decide to check the aggregate
> every so often and see if it was still correct (and update it if not).
> The good news is that he hasn't lost any data, and could change his
> gadget to work without that state at any time.
>
> I'll point that out in future talks.
>
--
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-wave-api?hl=en.
