A request tag element is one generated by a client application to request information about a routing platform’s current status or configuration, or to change the configuration. A request tag element corresponds to a CLI operational or configuration command. It can occur only within an <rpc> tag element. For information about the <rpc> tag element, see Sending a Request to the JUNOScript Server.
A response tag element represents the JUNOScript server’s reply to a request tag element and occurs only within an <rpc-reply> tag element. For information about the <rpc-reply> tag element, see Parsing the JUNOScript Server Response.
The following example represents an exchange in which a client application emits the <get-interface-information> request tag element with the <extensive/> flag and the JUNOScript server returns the <interface-information> response tag element.
 |
Note: This example, like all others in this guide, shows each tag element on a separate line, in the tag streams emitted by both the client application and JUNOScript server. In practice, a client application does not need to include newline characters between tag elements, because the server automatically discards such white space. For further discussion, see Spaces, Newline Characters, and Other White Space. |
For information about the xmlns:junos and xmlns attributes, see Parsing the JUNOScript Server Response and Requesting Operational Information.
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |