DACS behavior about 2 similar users .
Hello, we are using RFA 8.1 C++ api to consume L1 and L2 market data. We want to understand If two object of rfa::common::client are created with same userid, and One object send Logout request to DACS then other object will also receive ComplEventEnum ?
Let's we have 2 object with same userid 'MST' , If we send logout from first MST object will second object receive ComplEventEnum along with first ?
Best Answer
-
Thank you for reaching out to us.
I assume that this question is about the Open DACS API (AuthorizationAgent::login() and AuthorizaionAgent::logout()).
10:44:36authorizationAgent::login() succeeded
10:44:36Received DACS Authorization Event...
User: jirapongse Position: 10.0.0.1/net
Status:Loggin
Status Code:NoStatusCode
Status Text: LoginResultPass:handle[4]
10:44:42authorizationAgent::login() succeeded
10:44:42Received DACS Authorization Event...
User: jirapongse Position: 10.0.0.1/net
Status:Loggin
Status Code:NoStatusCode
Status Text: LoginResultPass:handle[5]
10:50:27AuthorizationAgent::logout() dialog is opened.
//Logout the first event stream (handle[4])
10:50:29authorizaionAgent::logout() succeeded
10:50:29Received Completion Event...
User: jirapongse Position: 10.0.0.1/net
Event Stream Closed: True
//Logout the second event stream (handle[5])
10:55:37authorizaionAgent::logout() succeeded
10:55:37Received Completion Event...
User: jirapongse Position: 10.0.0.1/net
Event Stream Closed: TrueIf the application calls the authorizationAgent::login() method twice with the same username, it will create two event streams. The logout() of the first event stream will not impact the second event stream.
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
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛