Transport Definitions Must be Unique

It is erroneous to define two or more transports with identical transport configuration values.

For example:

  • Do not configure two transport definitions that access the same shared memory segment.
  • Do not configure two transport definitions with the same multicast send group and listen groups.

The scope of this prohibition is even wider than a single realm. If two or more realms exist within the same network, then violating this rule can result in interference between the realms.

Do not bend this rule as a technique to bridge between two realms. Instead, develop a custom application to translate messages between realms. Such an application would straddle the realms, connecting to two FTL servers, which maintain the distinct realm definitions for their respective realms. (The translation application must pay special attention to the formats of messages as they cross between realms.)

Related concepts