Serial and industrial data integration, gateway protocols and application-level buffering. Evaluate data ordering, duplicates and recovery independently of whether a network connection has been restored.
In Mosquitto 2.0.20, enabling persistence does not make every MQTT acknowledgement a synchronous database checkpoint. The broker can acknowledge a retained QoS 1 publication while its newest state is still only in memory. Define restart expectations from persistence configuration and observed checkpoint behavior, then test orderly exit and abrupt process termination separately. This guide pins…
Review a broker bridge as a directed graph of broker-and-topic states. For every forwarding rule, compute the destination topic after prefix removal and addition, then ask whether another rule can send it back into the original export space. Distinct ingress and egress prefixes make that analysis easier and reduce reliance on implementation-specific loop suppression. This…
MQTT wildcards match topic levels, including empty levels, and a leading wildcard does not cover Topic Names beginning with a dollar sign. Build a concrete filter-versus-topic truth table before declaring that a subscription covers every device or every broker diagnostic. The most revealing cases are often a parent topic, a trailing slash or a system…
Validate an MQTT topic in layers: encoded byte length, well-formed UTF-8, MQTT’s prohibited and discouraged code points, then Topic Name grammar. A generic UTF-8 decoder alone is insufficient because U+0000 is valid Unicode encoding but forbidden in MQTT UTF-8 strings. Conversely, some well-formed code points are discouraged rather than universally forbidden, so keep protocol requirements…
An OPC UA Call identifies both the Object or ObjectType context and the Method. Validate that relationship and the ordered argument signature before submitting the request. Knowing a Method NodeId is insufficient: the same method definition can belong to different instance contexts, while a valid-looking argument list can still violate datatype, rank or application constraints….
A successful OPC UA Read or Write service response does not mean every requested item succeeded. Decode two levels: the ResponseHeader serviceResult, then the ordered result for each operation. Preserve that distinction through cache updates, command reporting and retry decisions instead of collapsing the batch into one success boolean. This guide pins OPC UA Part…
Select an OPC UA endpoint by intersecting the complete EndpointDescription with the client’s capabilities and deployment policy. The required transport, message-security mode, channel SecurityPolicy and UserTokenPolicy must all be compatible. Choosing the first familiar URL or the highest securityLevel can still leave the client unable to authenticate the intended user. This guide pins OPC UA…
A completed HistoryRead page proves only that one response was processed. Finishing a requested time range requires exhausting each node’s continuation sequence, preserving operation and value statuses, and interpreting bounds according to the original request. Even then, the result is the historian’s stored data, which may be compressed or subject to retention; it is not…
An EventFilter has two independent jobs: whereClause decides which ordinary Events qualify, and selectClauses define the ordered fields returned for each qualifying Event. A successful subscription or a nonempty event stream does not prove that the requested event types and fields are correct. Validate construction results, runtime field values and the client’s positional decoder separately….
An unknown ExtensionObject can be retained as an identified opaque payload, but that does not make arbitrary forwarding safe. The bridge must preserve its encoding identity and bounded body, establish that the destination understands that encoding, and prove that namespace-sensitive content remains valid in the destination context. If the operation requires field interpretation or encoding…