Determine Connection State in REDI
In general the documentation and sample code provided only make passing reference to the RediLib.Application object and it's use. Were it not for the sample code there's not enough documentation on creating a Redi connection. Based on this I'm left in the dark a bit on how I am to determine if my connection to Redi Plus is active.
There are a few callbacks
within the RediLib.Application object that don’t seem to ever be called.
Namely Connected and Disconnected. None of the demo code seemed to make
any use of them and I was wondering if they were deprecated or just called
infrequently. I've tried turning off the
RediPlus app while connected to see if it would create a disconnect event and it did not.
This lead me wondering how will I know if I’m connected to REDI? Sure
there’s a few callbacks when I connect giving me msg 14 stuff. But if the
RediPlus App dies or the connection drops is there any way for my code to know
about it?
I'm attempted to call the method IsApplicationReady every few minutes but it throws an exception.
The API documentation doesn't talk about it and the sample code doesn’t seem
to cover it either.
Thanks,
Best Answer
-
This is one way to do it.
public MainWindow()
{redi = new RediLib.Application();
redi.ApplicationClosed += Redi_ApplicationClosed;
InitializeComponent();
Side.Items.Add("Buy");
Side.Items.Add("Sell");
}
private void Redi_ApplicationClosed()
{Console.WriteLine("Application Closed");
return;
}
I tested this and I see "Application Closed" in Visual Sudio console when I close the R+ application while the API application is running.
Calling isApplicationReady ahead of logging into R+ leads to a few problems. The first being you will initialize and call RediLib objects/methods, which assumes R+ connection. This leads us to a fundamental assumption about API applications, which is that we assume R+ is up and running ahead of running the API applcation.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛