User guide

Viz Engine Administrator’s Guide

The preferred method to send data is to use the ‘SendToSMM’ library (or an equivalent)

to send the data to the individual Viz Engines.

The communication protocol for the import of Shared Memory data depends on the

type and final output of the data. There are set protocols to use with large amounts of

data, in which all of the data must reach its destination graphic, and also where large

amounts of data must be received, quickly, but some loss of data is acceptable.

For use cases see:

• TCP Protocol

• UDP Protocol

• Plugin API

• Command Interface

Note: It is also possible to import data through Multicast. This method is not

recommended as it can pollute the network.

This section contains information on the following topics:

• TCP Protocol

• UDP Protocol

• Plugin API

• Command Interface

9.1.1 TCP Protocol

The SHM TCP communication protocol guarantees a reliable delivery of packages. It is

a much more efficient than the Command Interface, but not as fast as the UDP Protocol

protocol.

Use cases for a TCP connection could be finance stocks and currencies, or election

result information, where the requirement is to deal with large amounts of information,

and all of this data must reach its destination graphic. A single piece of lost data can

have economic consequences, falsify charts, show mathematically wrong results, etc.

A TCP connection to a Viz Engine can be held open for a long time (this is

recommended), and should not be opened and closed between sending variables.