Table of contents
The TurboExchange message format is a precise way of defining messages, to be sent over the network. It defines all the same fields that Turbo Dispatch does, except it also defines which fields may be used with which message, which in the past has caused confusion, and incompatibility problems.
Furthermore, it integrates better with modern programming techniques, and is much more efficient in processing time, and bandwidth.
However, legacy software needs still to be supported, so the .NET connector has a built in compatibility layer, than can convert from one format to the other, and back again. This is completely automated, and the developer has no need to understand legacy protocols. Should there be a requirement to stay with legacy protocols, there is the flexibility to do that too.
Messages sent in the old Turbo Dispatch format, are converted to the new TurboExchange format, before being serialized, and transmitted over the network. Incoming message can be optionally converted back, into the legacy Turbo Dispatch format when received.
See source code examples on how to archive this.
