Purge Properties
Either a Device or Data Orchestrator may tell the remote host the set properties list. Any property that is not part of the list will be deleted from any cache or database.
This task is called purge properties in Data Orchestrator jargon, and it is performed by publishing a the list of known set properties to /control/consumer/properties or /control/producer/properties.
Purge Properties payload is a zlib deflated plain text, with an additional 4 bytes header. The additional 4 bytes header is the size of the uncompressed payload, encoded as big endian uint32.
The uncompressed plain text payload has the following format (in BNF like syntax):
properties ::= properties_list
properties_list ::= properties_entry ";" properties_list | properties_entry
properties_entry ::= interface_name path
The following example is the inflated payload:
com.example.MyInterface/some/path;org.example.DraftInterface/otherPath
This protocol feature is fundamental when a device has any interface with an allow_unset mapping, purge properties allows to correct any error due to unhandled unset messages.