I am in charge to migrate a MLIP based C#/.NET application to WebSocket API. The application is basically contributing RICs data. I have now looked through the documentation and the C# sample code, and have some initial questions:
1. Redundancy concept:
In MLIP, having parallel connections to two independent servers with automatic failover was a requirement to achieve high availability. I could not find anything like this in the WebSocket API documents.
How is the redundancy / high availability / resilience concept implemented in WebSocket API (if there is any)?
Some of your samples implement an authentication request prior to login, while others do the login immediately.
Is the authentication request to the auth server always mandatory when contributing data?
3. Ping / Pong
The documentation states, that either side can actively send Ping requests, while to should respond such requests by a Pong.
What is the recommended strategy when implementing a Contribution application with high availability demands: Should we actively issue Pings, and what would be a reasonable interval?
4. Contribution workflow
If I have understood correctly, data contribution is implemented by using Post messages. This requires opening an event stream and issuing an Item request before we can send a Post message for this RIC.
Do we have to wait for the Item response message, before we can send the post message?