When a program instance sends a message, it is queued in a local data store, until it has been successfully transferred to the ISB. Messages in an outbound queue on the ISB are stored until they are successfully received by the retrieving program instance.
If your program is trying to send or receive messages but is experiencing a temporary loss of Internet connectivity, then the API automatically enters into a retry mode and connects to the ISB once the issue is resolved.
With assured information delivery, a core feature of Linxter, even if your program instance loses its network connection during the sending or receiving of a message, or if another failure interrupts the process, the transaction resumes with the message intact whenever the issue is resolved.
Another reliability and efficiency feature built into Linxter is chunking. For example, let’s say you are sending a message with a 100MB file attachment, and after transmitting 70MBs, the sending or receiving program loses its Internet connection. When the connection is re-established, the process picks up from where it left off. Reliability features like this are especially important with wireless (and its frequent interruptions in connectivity) becoming the norm.
Try It For Free