The Cúram developer and the remote application developer need to agree on the format(s) of the messages passed between the two systems. This involves:
The default encoding method can be used for each field; but, see Encoding Methods for Fundamental Types and Using Customized Encoding/Decoding Classes for how a custom encoding methodology may be implemented.
Like the encoding, the encoded length of each field depends on the type of the field and - for some datatypes - its length as specified in the model. See Encoding Methods for Fundamental Types for information on lengths of datatypes. The length of the field can be changed by implementing a custom mapper for the field.
The fields appear in the message in the same order as they appear in the struct in the meta-model. The tool-bar contains a facility for changing the order of struct attributes if required.