ernally, and cleanup is 100% guaranteed (no kernel-persistent resources are involved in serialization of structured messages).<ul>
<li>In terms of simplicity specifically: it is not required to operate within <a class="el" href="namespaceipc_1_1session.html" title="Flow-IPC module providing the broad lifecycle and shared-resource organization – via the session conc...">ipc::session</a> at all; whereas <code>Serializa_via_*_shm</code> are so required.<ul>
<li>Subtlety: One <em>can</em> operate the SHM-base