Andy Bierman writes:
Hi,
Use of NP-containers are subjective, based on how you want to
organize your data. The extra layer of containment may be a
waste, but it sometimes has a purpose
- 2 or more sibling lists with lots of entries can be mixed in
JSON,
so
On Wed, Dec 16, 2015 at 9:04 AM, Christian Hopps wrote:
>
> Andy Bierman writes:
>
> Hi,
>>
>> Use of NP-containers are subjective, based on how you want to organize
>> your data. The extra layer of containment may be a waste, but it sometimes
>> has a
> On 16 Dec 2015, at 18:04, Christian Hopps wrote:
>
>
> Andy Bierman writes:
>
>> Hi,
>>
>> Use of NP-containers are subjective, based on how you want to organize your
>> data. The extra layer of containment may be a waste, but it sometimes has a
> On 16 Dec 2015, at 18:08, Martin Bjorklund wrote:
>
> Anees Shaikh wrote:
>> I'm not suggesting this is necessarily standard behavior :-)
>
> I think this demonstrates that it is probably not a good idea to
> design (standard) data models to optimize
Anees Shaikh writes:
hi Chris, in OpenConfig models we use enclosing containers on
lists based on feedback from some implementors who claimed that
it made it more efficient to, for example, retrieve the entire
list (ask for the container), retrieve the keys in the list
Andy Bierman writes:
> Hi,
>
> Use of NP-containers are subjective, based on how you
> want to organize your data. The extra layer of containment
> may be a waste, but it sometimes has a purpose
>
> - 2 or more sibling lists with lots of entries can be mixed in JSON,
>
Hi,
Use of NP-containers are subjective, based on how you
want to organize your data. The extra layer of containment
may be a waste, but it sometimes has a purpose
- 2 or more sibling lists with lots of entries can be mixed in JSON,
so putting each list in its container prevents that.
-