I have a user (logged in from same IP) which is using two different applications A and B
Application A uses Open Dacs for entitlement checking to get streaming market data
Application B uses UPA to get streaming market data
Now, if Application A were to disconnect from DACS (using logout functionality from open dacs), what happens to the session from Application B
Does Application B get disconnected as well and stop streaming data?
What is the ideal way of managing these situations where a same user using same IP uses two different ways to entitle and stream data?
In terms of connections - the Open DACS API connects to a Dacs Sink Daemon, whereas your UPA consumer connects to a provider / source - typically the ADS (Advanced Distribution Server).
The ADS server will be unaware of any connection your other application has with Dacs Sink Daemon.
Even from the same UPA application, you could if required, create two separate logins + connections to the same server. When you logged out + closed one connection, the other should continue to stream data. Each login is considered a separate event stream.
The UPA application B should have its own connection / mount to the ADS - independent of Application A.
Each login is treated as a separate mount / connection - so disconnecting one should not affect the other.