Optionally, a client application can include one or more attributes in the opening <rpc> tag for each request. The client application can freely define attribute names, except as described in the following note. The JUNOScript server echoes each attribute, unchanged, in the opening <rpc-reply> tag in which it encloses its response. A client application can use this feature to associate requests and responses by including an attribute in each opening request tag that assigns a unique identifier. The JUNOScript server echoes the attribute in its opening <rpc-reply> tag, making it easy to map the response to the initiating request.
 |
Note: The xmlns:junos attribute name is reserved. The JUNOScript server sets the attribute to an appropriate value on the opening <rpc-reply> tag, so client applications must not emit it on the opening <rpc> tag. For more information, see xmlns:junos Attribute. |
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |