Re: [netconf] restconf collections

[Kent Watsen <[e-mail]>]

> The <get-bulk> operation is not stateful.
>  http://www.netconfcentral.org/modulereport/yumaworks-getbulk <http://www.netconfcentral.org/modulereport/yumaworks-getbulk>
This RPC is effectively 1-1 with RC query params approach being discussed.  I like it.

The “count” param is like “limit”, and “list-test” is like a “where”.

One difference is that <get-bulk> uses "last-keys” instead of an integral “offset”.   Any thoughts about the pros and cons?  I imagine performance depends on the backend database used.  For instance, SQL supports “offset” so, to support "last-keys” instead would entail a first query to determine the offset for a key.

Missing is a “sort”.  That said, of the four params mentioned (limit, offset, where, sort), it might be least important.  At least, a general sort is…and then there is the nasty issue of sorting a user-sorted list.  A likely must-have fallback would be “direction” so, e.g., queries return the most-recent (not the oldest) entires in a time-series list (e.g., a log).  A “direction” parameter would also work well on a user-sorted list.


> There are 3 completely different approaches:
> 
>   1) stateless
>   2) stateful
>   3) stateful snapshot
> 
> How to efficiently iterate through data that is changing constantly?
> This problem is harder than it looks.

Agreed.  I recommend we NOT try to solve that problem.


K.