clarified docs

This commit is contained in:
Davis King 2012-07-15 14:16:37 -04:00
parent bcdf2992c6
commit d13c84fba0
1 changed files with 6 additions and 4 deletions

View File

@ -985,8 +985,9 @@
We do this because Google protocol buffers are not
<a href="https://developers.google.com/protocol-buffers/docs/techniques#streaming">self-delimiting</a>
on their own. This means that you can't write more than one protocol buffer object to an output stream unless you include some kind
of delimiter between the messages. So dlib takes care of this for you by encapsulating each protocol buffer message inside a serialized
std::string object.
of delimiter between the messages.
So dlib takes care of this for you by prefixing each message with its length in bytes. The number
of bytes is encoded using the same scheme that serialize(int,ostream) uses.
</p>
</description>
@ -1008,8 +1009,9 @@
We do this because Google protocol buffers are not
<a href="https://developers.google.com/protocol-buffers/docs/techniques#streaming">self-delimiting</a>
on their own. This means that you can't write more than one protocol buffer object to an output stream unless you include some kind
of delimiter between the messages. So dlib takes care of this for you by encapsulating each protocol buffer message inside a serialized
std::string object.
of delimiter between the messages.
So dlib takes care of this for you by prefixing each message with its length in bytes. The number
of bytes is encoded using the same scheme that serialize(int,ostream) uses.
</p>
</description>