pub struct Writer {
pub node: NodeId,
pub fabric: FabricIndex,
}Expand description
Who holds a claim — §7.15.2’s Atomic Writer ID, together with its fabric.
§7.15.3 keys a state on both: the same node id on two fabrics is two different clients, and letting one inherit the other’s claim would let a second administrator commit writes the first had staged.
Fields§
§node: NodeIdThe peer’s operational Node ID, from the session.
fabric: FabricIndexThe accessing fabric.
Implementations§
Source§impl Writer
impl Writer
Sourcepub fn from_context(ctx: &InteractionContext<'_>) -> Option<Self>
pub fn from_context(ctx: &InteractionContext<'_>) -> Option<Self>
The writer an interaction identifies, or None when it cannot hold a claim.
§7.15.6.4: “If an AtomicRequest command is received without an accessing fabric, the
server SHALL return a status code of INVALID_COMMAND”, and likewise for a writer id
that is “either unavailable or not a valid Operational Node ID”. Both are None here.
A PASE session has no operational node id, and a group message has no peer at all, so neither can begin an atomic write — which is right: an atomic write is a claim held across several messages, and a claim needs somebody to be held by.