Data
|
Although the data subscriber provisions support for temporal processing by receiving historical data from a remote source, the adapter opens sockets and does not need to be engaged within an actual temporal IaonSession, therefore this method normally returns false to make sure the adapter doesn't get instantiated within a temporal session.
Setting this to true means that a subscriber will be initialized within a temporal session to provide historical data from a remote source - this should only be enabled in cases where (1) there is no locally defined, e.g., in-process, historian that can already provide historical data for temporal sessions, and (2) a remote subscriber should be allowed to proxy temporal requests, e.g., those requested for data gap recovery, to an up-stream subscription. This is useful in cases where a primary data subscriber that has data gap recovery enabled can also allow a remote subscription to proxy in data gap recovery requests. It is recommended that remote data gap recovery request parameters be (1) either slightly looser than those of local system to reduce the possibility of duplicated recovery sessions for the same data loss, or (2) only enabled in the end-most system that most needs the recovered data, like a historian.