Hi Lou,
>>>I know that this is a difference between the solutions, but I don’t see it
>>>listed as a requirement. There is a requirement to return the diff, but
>>>that’s all. Is there actually a need to return both sets of data? - or is
>>>this just a desire for the diff to be able t
On 09/02/2016 15:42, Kent Watsen wrote:
Can you please suggest an approach of how to return a single tree that
contains the data from two separate datastores (where the leaf paths may
overlap)? I think that the approach would need to work both for get
requests and also notification data.
Kent,
On 2/9/2016 10:42 AM, Kent Watsen wrote:
>
>
>
>> Can you please suggest an approach of how to return a single tree that
>> contains the data from two separate datastores (where the leaf paths may
>> overlap)? I think that the approach would need to work both for get
>> requests and also
>Can you please suggest an approach of how to return a single tree that
>contains the data from two separate datastores (where the leaf paths may
>overlap)? I think that the approach would need to work both for get
>requests and also notification data.
I know that this is a difference betw
On 08/02/2016 21:37, Martin Bjorklund wrote:
Robert Wilton wrote:
On 08/02/2016 19:41, Martin Bjorklund wrote:
Hi,
Robert Wilton wrote:
Hi Martin,
On 08/02/2016 13:45, Martin Bjorklund wrote:
Robert Wilton wrote:
On 06/02/2016 00:41, Andy Bierman wrote:
[...]
IMO, this solution is
On 08/02/2016 16:20, Juergen Schoenwaelder wrote:
On Mon, Feb 08, 2016 at 01:21:52PM +, Robert Wilton wrote:
So, IIRC, your concern is specifically that a generic YANG client
library cannot validate that the RPC reply is well formed against the
schema without knowledge about the request.
