Does Elektron Websocket API support Warm Standby?

@ron.bove

Thanks for reaching out to us.

It should be if the WebSocket server supports Warm Standby. You can check this from the login refresh message sent by the server.

    {
        "ID": 1,
        "Type": "Refresh",
        "Domain": "Login",
        "Key": {
            "Name": "...",
            "Elements": {
            ...
                "SupportStandby": 1,
                "SupportStandbyMode": 3,
...
            }
        },
      ...
        }
    }

If the server supports Warm Standby, you can use WebSocket API to implement this feature in the client's application.

You can see the sample messages from the postman examples. For more information, please also refer to the Introduction to Refinitiv Real-Time SDK Warm Standby Feature article.

I hope that this information is of help.

Thank you both @Jirapongse and @Gurpreet for your response. @Gurpreet , that was going to be my next question. What are the complexities of establishing and maintaining multiple websocket connections and do we have any examples of creating "login generic messages" in JSON, required to inform the provider of its active/standby state?

Thanks @Gurpreet, At this point we are just trying to confirm that its technically feasible, using the Websocket API, which it appears to be, and what's the relative complexity to implement such a solution. We appreciate the offer but its not necessary right now.

FYI:

I was looking into this earlier and did note that the ADS / RTC Sys Admin manuals (v 3.6.3) state that Warm Standby is only supported for RSSL type connections:

ADS Sysadmin manual section 20.2

A similar statement is present in the RTC 3.6.3 document (section 7.3)