-RMR is designed to provide an insulation layer between user
-applications and the actual transport mechanism. Initially
-RMR was built on top of the third-party library Nanosmg,
-shortly after was ported to the third-party library NNG
-(Nanomsg Next Generation), and then was ported to an
-internally developed socket library called SI95. RMR presents
-the same API to the user application regardless of the
-underlying transport library, but the resulting output when
-compiling RMR is always a transport-specific library. As an
-example, ``librmr_nng.a`` is the library generated for use
-with the NNG transport.
-
-As such the library source is organised into multiple
-components:
-
- .. list-table::
- :widths: auto
- :header-rows: 0
- :class: borderless
-
- * - **common**
- -
- Source in the common directory is agnostic to the underlying
- transport mechanism (Nanomsg, NNG, SI95, ..), and thus can be
- used when generating either library.
-
- * - **nano**
- -
- Source which is tightly coupled with the underlying Nanomsg
- library. (Nanomsg has been deprecated, but the RMR source
- remains as an example.)
-
- * - **nng**
- -
- Source which is tightly coupled with the underlying NNG
- library. (NNG has been deprecated, but the RMR source remains
- as an example.)
-
- * - **si**
- -
- Source which is tightly coupled with the underlying SI95
- library.
-
-
-
+RMR is designed to provide an insulation layer between user
+applications and the actual transport mechanism. Initially
+RMR was built on top of the third-party library Nanosmg,
+shortly after was ported to the third-party library NNG
+(Nanomsg Next Generation), and then was ported to an
+internally developed socket library called SI95. RMR presents
+the same API to the user application regardless of the
+underlying transport library, but the resulting output when
+compiling RMR is always a transport-specific library. As an
+example, ``librmr_nng.a`` is the library generated for use
+with the NNG transport.
+
+As such the library source is organised into multiple
+components:
+
+ .. list-table::
+ :widths: auto
+ :header-rows: 0
+ :class: borderless
+
+ * - **common**
+ -
+ Source in the common directory is agnostic to the underlying
+ transport mechanism (Nanomsg, NNG, SI95, ..), and thus can be
+ used when generating either library.
+
+ * - **nano**
+ -
+ Source which is tightly coupled with the underlying Nanomsg
+ library. (Nanomsg has been deprecated, but the RMR source
+ remains as an example.)
+
+ * - **nng**
+ -
+ Source which is tightly coupled with the underlying NNG
+ library. (NNG has been deprecated, but the RMR source remains
+ as an example.)
+
+ * - **si**
+ -
+ Source which is tightly coupled with the underlying SI95
+ library.
+
+
+