anchor.diff:  | Authors' preferred use case      | distributed  computing | financial / trading | distributed  computing | platforms /  sandboxing | financial / trading | games
   |===============
   
  -NOTE: The Binary YAML format can be automatically converted to YAML without any knowledge of the schema as the messages are self describing.
  -
  -NOTE: You can parse all the expected fields (if any) and then parse any remaining fields. As YAML supports object field "names" or keys, these could be Strings or even Object as keys and values.
  +NOTE: The Binary YAML format can be automatically converted to YAML without any knowledge of the schema, because the messages are self-describing.
  +
  +NOTE: You can parse all the expected fields (if any) and then parse any remaining fields. As YAML supports object field names (or keys), these could be strings or even objects as keys and values.
   
   Based on https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-sbe.html
   
  
positive.code:    long id = counter.getAndAdd(1);
  ----
  
  Other types such as 32 bit integer values and an array of 64-bit integer values are supported.
      
  == Compression Options
  
  * no compression
  * Snappy compression (planned)
  * LZW compression (planned)
  
  == Bytes options
  
  Wire is built on top of the Bytes library, however Bytes in turn can wrap
  
  * ByteBuffer - heap and direct
  * byte\[\] (via ByteBuffer)
  * raw memory addresses.
  
  == Uses
  
  Wire will be used for:
  
  * file headers.
  * TCP connection headers where the optimal Wire format actually used can be negotiated.
  * message/excerpt contents.
  * the next version of Chronicle Queue.
  * the API for marshalling generated data types.
  
  == Similar projects
  
  === SBE
  
  Simple Binary Encoding is designed to do what it says.
      It's simple, it's binary and it supports C++ and Java.  It is 
      designed to be a more efficient replacement for FIX. It is not limited to FIX 
      protocols and can be easily extended by updating an XML schema.
      
  XML, when it first started, didn't use XML for it's own schema files, and it's not
     insignificant that SBE doesn't use SBE for it's schema either.  This is because it is
     not trying to be human readable. It has XML which, though standard, isn't designed
     to be particularly human readable either.  Peter Lawrey thinks it's a limitation that it doesn't
     naturally lend itself to a human readable form.
     
  The encoding SBE uses is similar to binary, with field numbers and fixed width types.  
     SBE assumes the field types, which can be more compact than Wire's most similar option 
     (though not as compact as others).
     
  SBE has support for schema changes provided the type of a field doesn't change.
     
  === msgpack
  
  Message Pack is a packed binary wire format which also supports JSON for 
      human readability and compatibility. It has many similarities to the binary 
      (and JSON) formats of this library.  c.f. Wire is designed to be human readable first, 
      based on YAML, and has a range of options to make it more efficient.
      The most extreme being fixed position binary.
      
   Msgpack has support for embedded binary, whereas Wire has support for
      comments and hints to improve rendering for human consumption.
      
  The documentation looks well thought out, and it is worth emulating.
  
  
negative.code: 
  Now you can choose which format you are using.  As the wire formats are themselves unbuffered, you can use them with the same buffer, but in general using one wire format is easier.
  
  [source, Java]
  ----
  Wire wire = new TextWire(bytes);
  // or
  