markqvist
commented
1 week ago Since the FIELD_CUSTOM concept was added, this will be the canonical way to include custom datatypes and external, tunneled protocols and formats in LXMF messages. This is a better approach, since we do not need to add specific fields for a long list of protocols, applications and datatypes that developers may want to transport inside LXMF messages.
For reference, here is a copy of the FIELD_CUSTOM section of LXMF.py:
# For usecases such as including custom data structures,
# embedding or encapsulating other data types or protocols
# that are not native to LXMF, or bridging/tunneling
# external protocols or services over LXMF, the following
# fields are available. A format/type/protocol (or other)
# identifier can be included in the CUSTOM_TYPE field, and
# the embedded payload can be included in the CUSTOM_DATA
# field. It is up to the client application to correctly
# discern and potentially utilise any data embedded using
# this mechanism.
FIELD_CUSTOM_TYPE = 0xFB
FIELD_CUSTOM_DATA = 0xFC
FIELD_CUSTOM_META = 0xFD
Enumerated the Cursor on Target protocol used in Team Awareness Kit systems into base LXMF definitions. Designated 0x20 in order to avoid any collisions in 0x00-0x1f space and to designate it as an additional field, not core to LXMF features.