Re: [yang-doctors] question regarding conditional/optional statements

[Juergen Schoenwaelder <[e-mail]>]

On Thu, Aug 17, 2017 at 01:02:44PM +0200, Jan Lindblad wrote:
> 
> The problem with #4 is that many clients faithfully implementing applications based on the advertised, standard model will break. To fix the breakage requires after the fact programmer intervention. Not very software-defined. The long term effect is that application developers ignore standard models since custom adaptation to each device's implementation is required anyway, if deviations are used more than very occasionally.
>

I again fail to see the difference here between #4 and #5. Simple
clients will fail in the same way. Option #4 allows smarter clients
that are able to determine upfront that they won't work with a certain
server.

Perhaps your logic is that a smarter client will still have to expect
that a server is not entirely implementing a model (i.e., doing #5)
with out documenting this, and hence since the smarter client has to
expect some servers to be 'incomplete' anyway you can equally well
expect all of them to be 'incomplete' and skip the effort to decide
upfront whether a server implements a model 'complete enough' for the
client to work.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <http://www.jacobs-university.de/>