From d13c84fba0c258e981e89b81c53620e962199a86 Mon Sep 17 00:00:00 2001 From: Davis King Date: Sun, 15 Jul 2012 14:16:37 -0400 Subject: [PATCH] clarified docs --- docs/docs/other.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/docs/other.xml b/docs/docs/other.xml index a6140f6bd..07cdb758c 100644 --- a/docs/docs/other.xml +++ b/docs/docs/other.xml @@ -985,8 +985,9 @@ We do this because Google protocol buffers are not self-delimiting 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.

@@ -1008,8 +1009,9 @@ We do this because Google protocol buffers are not self-delimiting 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.