This service allows a correlator to provide access to market data that it receives from an adapter to other client correlators.
This service is used to bridge the com.apama.marketdata interface between two correlators. One correlator, connected to an adapter, acts as a server. The other correlator as a client. To perform the bridging, this monitor needs to be injected in the server correlator and an instance created by sending in the ConfigureServerSideBridge event. The two correlators must be connected to each other, and the channels in the configuration events have to match those of the engine connections.
This service will listen for depth/tick subscriptions that will have been forwarded to the server by the client. It will then setup listeners for the tick/depth events as well as the error events. When these fire, the service emits the events back to the client correlator. The service will also listen for the unsubscribe events from the client in order to destroy these listeners.
This service will also monitor the connection by using the IAFConnectionMonitor component, note that this means that the IAFStatusFaker must be running on the client correlator. Setting up instances of The IAFConnectionMonitor will normally be done by the adapter bridging configuration service. When a connection goes down, this monitor will unsubscribe to the adapter. When it comes back up, it will re-subscribe.