e.g. setValue currently filters out the peer that called it but is filtered out of the update. The initiating peer should be included in the broadcast.
This makes sense given that the service could apply constraints and change the value that was actually updated.
Also helps identify the case where updates are never applied (which does happen in our installed base).
to do: broadcast PushUpdates to all connected peers. No filtering needed, until subscriptions are supported.
e.g.
setValuecurrently filters out the peer that called it but is filtered out of the update. The initiating peer should be included in the broadcast.This makes sense given that the service could apply constraints and change the value that was actually updated.
Also helps identify the case where updates are never applied (which does happen in our installed base).
to do: broadcast PushUpdates to all connected peers. No filtering needed, until subscriptions are supported.