> On 24 Jun 2025, at 16:43, Andriy Sultanov <sultanovand...@gmail.com> wrote:
>
> But I think this only covers part of the problem. Looking at the concrete
> case of
> xenopsd and Windows VMs, xenopsd cares about most of the nodes it receives
> watch events from, the issue is that it doesn't know when these are grouped
> together in one way or another.
Is the common case that a client wants to observe the changes rather than just
knowing that a change occurred? If so, it seems transmitting changes as part of
a watch event (rather than forcing the client to traverse the tree) would be a
better protocol. That would suggest to introduce a new kind of watch that
reports changes at the end of a transaction. The size of the event would depend
on the size of the change.
— C
