"Alexander Clemm (alex)" <[email protected]> writes: > Thanks, Martin, this is very clear. > > (Too bad actually - I could see applications for this.)
Making this possible for anydata would be a useful improvement over anyxml but that would require the server to be able to parse data submitted in any supported encoding into the same data tree representation as "normal" data nodes. Lada > > --- Alex > > -----Original Message----- > From: Martin Bjorklund [mailto:[email protected]] > Sent: Monday, October 05, 2015 2:21 PM > To: Alexander Clemm (alex) <[email protected]> > Cc: [email protected]; [email protected]; > [email protected]; [email protected] > Subject: Re: [netmod] anydata interaction with yang-patch and edit config > > "Alexander Clemm (alex)" <[email protected]> wrote: >> Hi, >> >> I have two quick questions with regards to anydata - related to the >> topic of the thread, but concerning a separate topic. >> >> (1) How does yang-patch interact with anydata? In particular, could >> you apply a yang-patch edit to a data node within the anydata? (While >> the module may not have been known at design time, it will be known at >> run time - so presume yes.) >> >> (2) How about edit-config? Can you use edit config to apply >> operations to nodes within the anydata, or just to the blob as a >> whole? (Again, I would assume you can, as the nodes will be known at >> run time.) > > The current text says: > > An anydata node is treated as an opaque chunk of data. This data > can be modified in its entirety only. > > > So the answer to both questions are "no". > > I don't think that the module necessarily must be known at run-time. > > > /martin -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
