Type
Defines a union between source server type and the message's type. Based on this union the consumer can decide the serialization strategy.
Serialization strategy
There are 2 serialization strategies that conclude if message is type PluginMessage or NonSignalMessage.
If sourceServerType is type of SourceServerType.PLUGIN then content holds type of PluginMessage.
If sourceServerType is type of SourceServerType.PLUGIN then content holds type of NonSignalMessage.
Note that signal-compliant messages are represented through message's types except HUB_MESSAGE
and REJECTED
. They can also, represented through PluginMessage model.