Based on the spike work, the actual logic for reading the recordings cannot be ported naively. Mainly because memory mapping is no longer an option, since recordings might be too big to fit in memory. 

So a specific file reader must be implemented, mainly capable of moving throughout the file among a pair of start recording and end recording commands. Place all the commands found in some memory buffer + notify the main replay client, when new data is available.