anchor.diff:  Across topics, there is no guarantee of ordering; if you want to replay deterministically from a system which consumes from multiple topics, we suggest replaying from that system's output.
   
   '''
  -===== *Tailers and file handlers clean up*
  +==== Tailers and file handlers clean up
   
   Chronicle Queue tailers may create file handlers, the file handlers are cleaned up whenever the associated chronicle queue's `close()` method is invoked or whenever the Jvm runs a Garbage Collection.
   If you are writing your code not have GC pauses and you explicitly want to clean up the file handlers, you can call the following:
  
positive.code: To reduce the creation of the file handles, chronicle queue cashes them lazily and when it comes to writing data to the queue files, care-full consideration must be taken when closing the files, because on most OS’s a close of the file, will force any data that has been appended to the file, to be flushed to disk, and if we are not careful this could stall your application.
  
  '''
  ===== *Pretoucher and its configuration*
  
  `Pretoucher` is a class designed to be called from a long-lived thread. The purpose of the Pretoucher
  is to accelerate writing in a queue. Upon invocation of the `execute()` method, this object will pre-touch
  
negative.code: If `DTO` makes use of custom serialisation then you should specify the interface to write to with `-i`
  
  ''''
  ==== High level interface for reading/writing
  
  Chronicle v4.4+ supports the use of proxies to write and read messages.
  You start by defining an asynchronous `interface`, where all methods have:
  