Rob Shakir
Rob Shakir
Thanks. I've added this to the OC WG meeting agenda for tomorrow.
Please can you provide the relevant mappings to other implementations that show how this would be supported across different implementations? Thanks, r.
Thanks. I think we need some clarifications here. We expect that the leaf-encoding is based on how the subscription is requested. In the case that the client wants JSON-encoded values,...
If a particular leaf is requested, then sending a scalar (not a JSON object is fine). A `json_val` of `10042` is completely valid: ``` >>> import json >>> json.loads("10042") 10042...
Thanks -- I'll take a look at this tomorrow.
Thanks for the question. We should add some clarifications here -- since I think we're underspecified for the `Subscribe` case currently. I think that both of the variants are acceptable...
Please sign the CLA (either being added to the corporate CLA your org has signed, or individually if your organisation permits this) for us to move this forward. Thanks! r.
The `atomic` flag means that all leaves under the prefix are always updated together within the same `Notification`. It cannot be split across multiple `Notification` messages. It should be expected...
I think there's a bigger conversation to have here - given that we have moved on quite significantly from the model that this describes. I'd propose that we look at...
I can take a look at this. Apologies for the latency.