Warning: This is a development version. The latest stable version is Version 7.0.0.

Integrating Rely

What is the best way to integrate Rely? The answer in this case is; it depends.

Let us expand a bit. From a hardware perspective no changes should be needed. Rely is a software only enhancement without any specific requirements for the hardware. From a software perspective it depends very much on the existing software architecture. But roughly we may consider two cases:

  1. The existing software uses a unreliable datagram oriented transport (such as UDP). This could be a video streaming application.

    In this case Rely can be directly integrated into the existing software’s networking layer. Typically this requires only small modifications to the existing software and provides the highest level of flexibility.

    If the existing application cannot be modified (i.e. Rely cannot be directly integrated), it is often possible to run Rely side-by-side with the existing application. Either by configuring the existing application to send all network traffic to Rely or by configuring Rely as a VPN like service that intercepts the application’s traffic transparently. See the Rely App for more information.

  2. The existing software uses a connection oriented transport (such as TCP). In this case Rely can still provide substantial benefits - since it can help stabilize TCP’s congestion control over error prone links. However, the integration needs to happen below TCP - similar to how a VPN works. There will be no benefit from integration Rely directly with the application. For an example of running Rely with TCP traffic see the Rely **App** for more information.

If your use-case do not fall within either of the two cases described, then feel free to reach out at support@steinwurf.com to discuss your use-case.