Package mxaccess_gateway.v1

Class MxaccessGateway.BulkReadResult

java.lang.Object
com.google.protobuf.AbstractMessageLite
com.google.protobuf.AbstractMessage
com.google.protobuf.GeneratedMessage
mxaccess_gateway.v1.MxaccessGateway.BulkReadResult
All Implemented Interfaces:
com.google.protobuf.Message, com.google.protobuf.MessageLite, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Serializable, MxaccessGateway.BulkReadResultOrBuilder
Enclosing class:
MxaccessGateway
public static final class MxaccessGateway.BulkReadResult extends com.google.protobuf.GeneratedMessage implements MxaccessGateway.BulkReadResultOrBuilder
 Per-tag result for ReadBulk. `was_cached` is true when the value came from
 an existing live subscription's last OnDataChange (the worker did not touch
 the subscription); false when the worker took the AddItem + Advise + wait +
 UnAdvise + RemoveItem snapshot lifecycle itself.

 On `was_successful = true`, `value`, `quality`, `source_timestamp`, and
 `statuses` carry the read data (from the cached subscription or the snapshot
 lifecycle, depending on `was_cached`) and `error_message` is empty. On
 `was_successful = false`, only `server_handle`, `tag_address`, `item_handle`
 (when allocated), `was_cached`, and `error_message` are populated; `value`,
 `quality`, `source_timestamp`, and `statuses` are left at their proto3
 defaults (null / 0 / null / empty) and must not be read as data — they are
 wire-indistinguishable from "value is null with quality bad" data and serve
 only as absent markers. ReadBulk has no `hresult` field by design (its
 outcomes are timeout / cache / lifecycle states, not MXAccess COM return
 codes — see `docs/DesignDecisions.md` "Bulk Command Family"). Per-tag
 failures populate `error_message` and never raise — callers iterate and
 inspect each entry.
Protobuf type mxaccess_gateway.v1.BulkReadResult
See Also: