The messages described here are expected to be encoded to binary using
CCBE. However, certain exceptions have been made
in order to keep each message type at a fixed size. Protocols such as this container protocol constitute
a
bootstrapping problem in
that, if all of the messages were defined in
Cedarbridge,
the two communicating parties would have to speak
Cedarbridge in order to ask each
other if they can both speak
Cedarbridge. We instead use the
Cedarbridge language to document the basic structure of the messages, but assume
that the protocol messages will be manually read, written, and parsed without necessarily using
Cedarbridge compiler generated code. For this reason, the protocol does
not use
Cedarbridge's versioning facilities.