On 2017-10-06 23:11, Xufeng Liu wrote:
During the design team discussion for TE and MPLS YANG modeling, we have received a request from implementers: How to minimize the number of NETCONF/RESTCONF RPCs to improve operation efficiency?
Especially for the case when the operator or client software
[Sorry, fat-fingered the send button]
Here's how the paths might be altered:
- ../../../../../explicit-paths/explicit-path/name
+ /explicit-paths/explicit-path/name
Back to your question, I guess that something could be done, but I'm unsure if
how important it would be relative to other work
My experience is that clients get the entire config in one call, and then can
perform such resolutions locally.
BTW, really long relative paths are harder to read than an absolution path.
../../../../../explicit-paths/explicit-path/name
On 10/6/17, 5:11 PM, "netmod on behalf of Xufeng Liu"
During the design team discussion for TE and MPLS YANG modeling, we have
received a request from implementers: How to minimize the number of
NETCONF/RESTCONF RPCs to improve operation efficiency? Especially for the
case when the operator or client software needs to retrieve the object
contents
