Manual page updates for v1.3.2

1 files changed, 83 insertions, 0 deletions

diff --git a/man/v1.3.2/nng_msg.5.html b/man/v1.3.2/nng_msg.5.html
new file mode 100644
index 00000000..b863975f
--- /dev/null
+++ b/man/v1.3.2/nng_msg.5.html
@@ -0,0 +1,83 @@
+---
+version: v1.3.2
+layout: manpage_v2
+---
+<h1>nng_msg(5)</h1>
+<div class="sect1">
+<h2 id="_name">NAME</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>nng_msg - message</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_synopsis">SYNOPSIS</h2>
+<div class="sectionbody">
+<div class="listingblock">
+<div class="content">
+<pre class="pygments highlight"><code data-lang="c"><span class="tok-cp">#include</span> <span class="tok-cpf">&lt;nng/nng.h&gt;</span><span class="tok-cp">
+</span><span class="tok-cp"></span>
+<span class="tok-k">typedef</span> <span class="tok-k">struct</span> <span class="tok-n">nng_msg</span> <span class="tok-n">nng_msg</span><span class="tok-p">;</span></code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description">DESCRIPTION</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>An <code>nng_msg</code> represents a single message sent between Scalability Protocols
+peers.
+Messages internally have a body, containing the application supplied
+payload, and a header, containing protocol specific routing and similar
+related information.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-tip" title="Tip"></i>
+</td>
+<td class="content">
+Using message-oriented functions is a good way to reduce the likelihood
+of data copies and improve application performance.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>Messages are allocated using the <a href="nng_msg_alloc.3.html"><code>nng_msg_alloc()</code></a>
+function, and are deallocated using the <a href="nng_msg_free.3.html"><code>nng_msg_free()</code></a>
+function.</p>
+</div>
+<div class="paragraph">
+<p>In addition there are other functions used to access message contents,
+including adding data to either the beginning or end of the message,
+automatic data conversion, and removing data from the beginning or end.
+These functions are designed to try to avoid copying message contents
+by making use of scratch areas at the beginning and end of the message.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_see_also">SEE ALSO</h2>
+<div class="sectionbody">
+<div class="paragraph text-left">
+<p><a href="nng_aio_get_msg.3.html">nng_aio_get_msg(3)</a>,
+<a href="nng_aio_set_msg.3.html">nng_aio_set_msg(3)</a>,
+<a href="nng_msg_alloc.3.html">nng_msg_alloc(3)</a>,
+<a href="nng_msg_body.3.html">nng_msg_body(3)</a>,
+<a href="nng_msg_dup.3.html">nng_msg_dup(3)</a>,
+<a href="nng_msg_free.3.html">nng_msg_free(3)</a>,
+<a href="nng_msg_header.3.html">nng_msg_header(3)</a>,
+<a href="nng_msg_header_len.3.html">nng_msg_header_len(3)</a>,
+<a href="nng_msg_len.3.html">nng_msg_len(3)</a>,
+<a href="nng_msg_realloc.3.html">nng_msg_realloc(3)</a>,
+<a href="nng_recvmsg.3.html">nng_recvmsg(3)</a>,
+<a href="nng_sendmsg.3.html">nng_sendmsg(3)</a>,
+<a href="nng_strerror.3.html">nng_strerror(3)</a>,
+<a href="nng.7.html">nng(7)</a></p>
+</div>
+</div>
+</div>