Skip to content

GitLab

"tests/git@developer.sourcefind.cn:OpenDAS/mmcv.git" did not exist on "428512f88abd956552fc390e902666c8e9b94593"
Commit d13c84fb authored by Davis King's avatar Davis King
Browse files

clarified docs

parent bcdf2992
Hide whitespace changes
Inline Side-by-side
Showing with 6 additions and 4 deletions
docs/docs/other.xml
View file @ d13c84fb
......@@ -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>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment