anchor.diff:  Any faster than about 20 times a second and it is just appears as just a blur and counter productive.
   
   It makes a lot sense for a desktop application to only receive as much data as it can handle, as much data as the person having to view it and to push back on the server when it cannot handle this data rate.
  -http://www.reactive-streams.org/[Reactive Stream] are an excellent way to model such client centric solutions.
  +http://www.reactive-streams.org/[Reactive Streams] are an excellent way to model such client centric solutions.
   
   ==== Producer Centric solution
   
  
positive.code: <2> the type of header is aliased as the name SCQStore.
  <3> the `writePosition` is the first bound value. It is the highest known byte which has been written to and is updated atomically.
  <4> the roll cycle is daily.
  <5> this class control how it will be indexed on demand.  This adds meta data entries for indexed lookup.
  <6> this is the highest message index which was acknowledged by a replica.
  
  For us a key feature of CQ is not just how the data structure is arranged,
  
negative.code: == What is Chronicle Queue?
  
  Chronicle Queue (CQ) is a persisted journal of messages.
  CQ supports concurrent writers and readers even across multiple JVMs on the same machine.
  Every reader sees every message and a reader can join at any time and still see every message.
  We assume you can read/scan through messages fast enough that even if you are not interested in most messages it will still be fast enough.
  These are not consumers as such and messages don't disappear after reading them.
  