Introduction
This document describes the API between TSS and TFT Routers. In general, TSS has an Event Queue containing First-In-First-Out (FIFO) “add” and “delete” events that are to be downloaded to the TFT Router, in order. The “add” event indicates that a TFN has been activated. The “delete” event indicates that the TFN has been deactivated. The following figure shows the relevant network elements for the TFT Router API. The arrow highlighted in red is the subject of this document.
The audience for this document is the development and quality assurance team of the protocol defined in this document. There are concepts in this document that assume the reader already understands protocols, such as TCP. The document also assumes specifically that the reader is already familiar with TSSRegistry™, TFNRegistry™, REST, and JSON.
Disclaimer: Any images in this article are intended to be used as a guide for educational purposes only and they may differ slightly from the Production Environment.
Event Queue Order
The TFT Router, on demand, requests events to be downloaded. The events MUST be downloaded in FIFO order. Each event must be completely processed by the TFT Router before the TFT Router can start to process the next event -- order is critical to the integrity of the downloaded data. If events are processed out of order, then activates could be processed before deactivates and result in the TFN having the wrong state at the TFT Router.