MQeKey objects can be attached to and used by an attribute object.
The Native attribute user interface is different from the C Binding attribute interface.
The C Binding attribute interface consists of two classes: MQeKey and MQeSharedKey. The MQeSharedKey is a subclass of MQeKey.
The Native attribute interface currently consists of two different classes: MQeKey (abstract) and MQeLocalKey. MQeLocalKey is a subclass of MQeKey. The following table describes the class correspondence between the Native attribute interface and the C Binding attribute interface.
* -------------------- ---------------------- * Native C Binding * -------------------- ---------------------- * MQeKeyBase MQeKey (part of) * MQeLocalKey MQeKey (part of) * not yet supported MQeSharedKey *
The MQeKey has only one method, mqeKey_free, and it is a polymorphic entry point to actual implementations of subclass free functions. Callers should use this polymorphic entry point to access subclass implemented methods.
The MQeLocalKey is a symmetric key (the same key used for both encoding and decoding) which can not be shared across network. It is must be initialized with an Ascii string seed, using mqeLocalKey_setKeySeed, before it can be used.
Class method correspondence:
* ----------------------- ---------------------- * Native C Binding * ----------------------- ---------------------- * mqeLocalKey_new mqeKey_new * mqeKeyBase_free mqeKey_free * mqeLocalKey_setKeySeed mqeKey_setLocalKey *