Get desktop application:
View/edit binary Protocol Buffers messages
ContextlessMsg is designed to carry a message of completely arbitrary type Because there is no context for the type embedded in the message, the opaque type must be dynamically added at runtime
Used in:
DynamicMsg is designed to test the dynamic message component The dynamic wrapper applied to ContextlessMsg is determined by dynamic_type
NestedMsg is designed to test the nested message component
SimpleMsg is designed to test that all three types of message fields, plain, map, and slice are handled by the protolator tool
Used in:
StaticallyOpaqueMsg is designed to test the statically opaque message component All fields are statically marshaled to the NestedMsg type
VariablyOpaqueMsg is designed to test the staticaly opaque message component The opaque type is determined by opaque_type