Re: [Netconf] RESTCONF depth parameter

[Andy Bierman <[e-mail]>]

On Fri, Dec 13, 2013 at 9:47 AM, Upendra Rajput (uprajput) <
[e-mail]> wrote:

>  Thanks Andy.
>
>  In your example for depth=2 why is LIST "playlist" omitted. It is at the
> same level as CONTAINER "library" and "player" are. So I was thinking it
> will be part of depth=2 output for the example module that is being used in
> the draft.
>
> GET /restconf/config/example-jukebox:jukebox?depth=2
>
>      {
>         "example-jukebox:jukebox" : {
>           "library" : [null],
>
>     "playlist": [null],   <<== Missing in your example for depth=2
>
>           "player" : [null]
>         }
>       }
>
>
>
Not based on the starting point (no depth parameter given).
I will add 1 or 2 playlists in the draft example.



>  Thanks
> ~Upendra
>
>

Andy



>
>   From: Andy Bierman <[e-mail]>
> Date: Friday, December 13, 2013 9:28 AM
> To: Cisco Employee <[e-mail]>
> Cc: "[e-mail]" <[e-mail]>
> Subject: Re: [Netconf] RESTCONF depth parameter
>
>
>
>
> On Thu, Dec 12, 2013 at 2:18 PM, Upendra Rajput (uprajput) <
> [e-mail]> wrote:
>
>>  Hi,
>>
>>  I was looking at the "depth" parameter example in RESTCONF draft
>> version 2 in section 3.8.1. There they have an example that will retrieve 2
>> levels of configuration data nodes from "example-jukebox" module. And the
>> result of retrieval is shown as:
>>
>>       {
>>         "example-jukebox:jukebox" : {
>>           "library" : {
>>             "artist" : {
>>               "name" : "Foo Fighters"
>>             }
>>           },
>>           "player" : {
>>             "gap" : 0.5
>>           }
>>         }
>>       }
>>
>>
>>
>
>
>  This example is wrong and needs to be fixed.
> The depth parameter is affected by the decision to make
> all YANG nodes be resources instead of just containers and lists.
> The example did not get updated to adjust for this change.
>
>  The example will be clarified so the starting data is shown, so it is
> clear what is begin filtered by the depth parameter:
>
>  GET /restconf/config/example-jukebox:jukebox
>
>        {
>         "example-jukebox:jukebox" : {
>           "library" : {
>             "artist" : {
>               "name" : "Foo Fighters"
>             }
>           },
>           "player" : {
>             "gap" : 0.5
>           }
>         }
>       }
>
> GET /restconf/config/example-jukebox:jukebox?depth=1
>
>      {
>         "example-jukebox:jukebox" : [null]
>      }
>
>
> GET /restconf/config/example-jukebox:jukebox?depth=2
>
>      {
>         "example-jukebox:jukebox" : {
>           "library" : [null],
>           "player" : [null]
>         }
>       }
>
>
> GET /restconf/config/example-jukebox:jukebox?depth=3
>
>       {
>         "example-jukebox:jukebox" : {
>           "library" : {
>             "artist" : [null]
>           },
>           "player" : {
>             "gap" : 0.5
>           }
>         }
>       }
>
>
>
>
>>  My question is since *both containers and lists* are defined as
>> resources then why *"list playlist"* is not included in the result shown
>> above ?
>>
>>  Will an error be returned when level is less then 1 ?
>>
>>
>  yes
>
>
>>  Also I will appreciate if you can provide sample of what will be
>> returned when depth is 1 and 3.
>>
>>
>>  Thanks
>>  ~Upendra
>>
>>
>
>  Andy
>
>