Under normal flow, Handler logs all the important aspects of its execution onto the file system. Log files also include original market data processed by the Handler. This information is usually saved for analysis of non-standard situations which may occur during use of the Handler. However, it also can be used to reproduce standard Handler's behavior for a certain period.
Once Handler was executed with logging enabled, it's possible to use log files for further replay. First of all, logs must be backed up (copied to another location) or the Handler's configuration must be updated to use another directory for new log files because the current implementation of the Handler doesn't support replay from the same folder in which new logs are stored.
Market data replay can be done with the help of start member. It accepts an instance of OnixS::Eurex::MarketData::ReplayOptions class containing a list of logs to be replayed.
Collection of log files can be either manually assigned or fulfilled from the provided folder.
Alternatively, it's possible to manually define a list of log files to be replayed. Manually manipulating list of log files allows replaying log files whose names differ from names used by the Handler.
From listener callbacks perspective, there's no difference whether the Handler processes market from the network or log files.
Sample application demonstrating Log Replay feature can be found in samples/Backtesting subfolder of distributive library package.