[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Difference between get and get-config

Balazs Lengyel wrote:

Hello,
Until now I interpreted this as:
The configuration will have many top nodes, one for every namespace. Or do we allow it that even for one namespace there will be multiple top level nodes? 

XSD does not support this.
There can only be one top-level element in a given namespace.



Balazs


Andy





Martin Bjorklund wrote:

Johan Rydberg <johan.rydberg@edgeware.tv> wrote:

Martin Bjorklund skrev:

Johan Rydberg <johan.rydberg@edgeware.tv> wrote:

What is the difference between get and get-config(running) with the
exception of <get/> returning device state information as well?

That is the difference.

Related question;

Reading the RFC I got the impression that the stores can only store a
single configuration (ie, a XML tree with data).  But extensions such
as notification and monitor introduces data parallel to the
configuration data (the 'top' node).

Also, on the NGO list Andy states the following:

   I don't use a real node called 'top'.  The <config> or <data>
   node is the conceptual 'top'.

Does this mean that the configuration data can be split in several
XML documents? 

Yes, in the sense that you can get e.g.

  <data>
    <interface xmlns="http://example.com/ns/interface";>
       ...
    </interface>
    <system xmlns="http://example.com/ns/system";>
       ...
    </system>
    <eventStreams xmlns="urn:ietf:params:xml:ns:netmod:notification">
       ...
    </eventStreams>
  </data>
    Each of these can be viewed as a separate XML document if you wish.



/martin

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>





--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>