Primary Rendezvous Request to a Subject, Secondary FTL Reply to an Inbox

A Rendezvous program sends a request message to a multicast subject, rather than to an inbox. The adapter detects that it is a multicast request message because it meets all of these criteria.

  • The subject of the message matches the subject attribute of a configuration tag.
  • The attribute of that tag specifies the name of an FTL field, called the reply field.
  • The realm defines the format such that the reply field has type TIB_FIELD_TYPE_INBOX.

To configure this case, ensure that the adapter configuration meets these three criteria.

The adapter arranges a mechanism through which an FTL program can reply to the Rendezvous request:

  1. The adapter gets the reply subject, namely, the Rendezvous inbox name where the requestor awaits a reply.
  2. The adapter maps that Rendezvous inbox to an FTL inbox within the adapter, called the reply inbox.
  3. In the FTL translation of the request message, the adapter stores the reply inbox in the reply field.
  4. Later, when an FTL program sends a reply to that reply inbox, the adapter receives it, translates it to a Rendezvous message, and forwards it to the reply subject. That reply subject is the Rendezvous inbox where the requestor awaits the reply.