The following tables list the members exposed by WriteRequestItemList.
Name | Description | |
---|---|---|
![]() | WriteRequestItemList Constructor |
Name | Description | |
---|---|---|
![]() | ItemPath | A portion of the namespace pointing to the data. The ItemPath is server specific and the client should not make any implications about its content, structure, or consistency across servers. ItemPath may or may not imply node, or server. If an XML-DA server was front ending a DA based server, then an example could be: \\NODE\OPC.DAServer.2. ItemPath is a hierarchical parameter. If ItemPath is Blank or missing at all levels of the hierarchy, then the ItemName is expected to be a fully qualified name. |
![]() | Items | The Write request allows the client to specify one or more of the following attributes of a value (Time, QualityField, LimitField, and VendorField). The servers must either support writing none of these qualifying attributes, or they must support writing all on a per item basis. Writes of only Value, or Value/Quality/Time/Bits are atomic writes. Either they all are written, or none are written. Examples of clients which might leverage this capability are simulation clients, or advanced control type clients. In both cases the client is generating the Item Value, and would benefit from the ability to write one or more of: Time, QualityField, LimitField, or VendorField. If the client specifies a subset of the attributes, then the server will only attempt to write the supplied subset. If a client attempts to write any value, quality, timestamp combination and the server does not support the requested combination (which could be a single quantity such as just timestamp), then the server will not perform any write and will return the E_NOTSUPPORTED error code. In the case of a quality other than Good (and if the server supports the writing of QualityField), the value should be some client specific default item value (typically 0 or a Null string), and will be ignored by the server. |