title: Best practices to reduce size for protobuf messages?
body: <p>I am sending positional/rotational data (vector3,quaternions) using protobuf-net messages from a client in c# to a server in c++.</p>
  
  <p>At the start I tried a hierarchical approach in the form of </p>
  
  <pre><code>Message Vector3
  { 
  int32 x = 1;
  int32 y = 2;
  int32 z = 3;
  }
  
  Message Transform
  {
  Vector3 trackedPos1 = 1;
  Vector3 trackedPos2 = 2;
  Vector3 trackedPos3 = 3;
  }
  </code></pre>
  
  <p>and the hierarchy grows larger and larger and with it the overhead from the protobuff messages. I can flatten the messages into a single one but it am not sure how managable it will become.</p>
  
  <p>So anyone got any idea how to tackle this with low overhead?</p>