Home / Docs / Which functions can be exchanged in part

Which functions can be exchanged in part

The generated Restricted Function Exchange table: every SPINE function this crate can serve a filtered read, a partial write or a filtered delete on, and every function it cannot.

SPINE admits thousands of implementation variations, and "which ones does this implement" is the first question an integrator has to answer. For Restricted Function Exchange the answer is a table, and this is it — generated from the same source the compiler reads, by cargo xtask rfe-table, so it cannot drift from what the engine does.

Of the 142 functions the SPINE payload defines, 141 can be exchanged in part: 98 are lists of identified entries and 43 are single values.

What the columns mean

Nothing in the XML Schemas links a data type to its selectors and elements filters — the link is a naming convention, which the generator resolves. Selectors choose which entries of a list a command addresses; elements choose which parts of them. A function with both can be read, written and deleted at either granularity; one with neither is exchanged whole.

This table is also what possibleOperations is derived from. A feature announces read.partial only for a function listed here, and a filtered request for anything else is answered errorNumber 8 rather than approximately — see Conformance.

A delete is a restricted exchange too: its selectors choose the entries and its elements choose the parts of them to remove, and a command may carry a delete filter and a partial-update filter at once. See Restricted Function Exchange.

Exchangeable in part

Whole function only

The schemas give one function no selectors and no elements filter, so there is nothing to narrow it by. A feature serving one announces read without partial, and a peer that sends a filter for it is answered errorNumber 8 — the honest answer, and the one that stops a client acting on a reply it thinks was filtered.

• resultData