NextCloud/dlib
1
0
Fork 0
mirror of https://github.com/davisking/dlib.git synced 2024-11-01 10:14:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

updated docs

Browse Source
This commit is contained in:
Davis King 2012-07-15 15:33:00 -04:00
parent 98c5e94a19
commit ab57847911
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/docs/other.xml
View File

@ -984,10 +984,10 @@
note that dlib::serialize() writes additional delimiting bytes at the start of each protocol buffer message.
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 prefixing each message with its length in bytes. The number
of bytes is encoded using the same scheme that serialize(int,ostream) uses.
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 prefixing each message with its length in bytes. In particular,
the number of bytes is encoded as a 32bit little endian integer.
</p>
</description>
@ -1008,10 +1008,10 @@
note that dlib::serialize() writes additional delimiting bytes at the start of each protocol buffer message.
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 prefixing each message with its length in bytes. The number
of bytes is encoded using the same scheme that serialize(int,ostream) uses.
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 prefixing each message with its length in bytes. In particular,
the number of bytes is encoded as a 32bit little endian integer.
</p>
</description>