BodgeMaster
/
NORM-mirror
mirror of https://github.com/USNavalResearchLaboratory/norm.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Generic editing and replaced dead URLs

pull/82/head
Lucas 2023-09-10 13:46:50 -07:00
parent 538bdee201
commit 8fadbc6ec2
1 changed files with 19 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
doc/NormDeveloperGuide.xml
View File

@ -13,19 +13,19 @@
<abstract> <abstract>
<para>This document describes an application programming interface (API) <para>This document describes an application programming interface (API)
for the <ulink url="http://norm.pf.itd.nrl.navy.mil/">Nack-Oriented for the <ulink url="https://www.nrl.navy.mil/Our-Work/Areas-of-Research/Information-Technology/NCS/NORM/">Nack-Oriented
Reliable Multicast (NORM)</ulink> protocol implementation developed by Reliable Multicast (NORM)</ulink> protocol implementation developed by
the Protocol Engineering and Advance Networking (<ulink the Protocol Engineering and Advance Networking (<ulink
url="http://cs.itd.nrl.navy.mil/">PROTEAN</ulink>) Research Group of the url="https://www.nrl.navy.mil/itd/ncs/">PROTEAN</ulink>) Research Group of the
United States <ulink url="http://www.nrl.navy.mil/">Naval Research United States <ulink url="https://www.nrl.navy.mil/">Naval Research
Laboratory</ulink> (NRL). The NORM protocol provides general purpose Laboratory</ulink> (NRL). The NORM protocol provides general purpose
reliable data transport for applications wishing to use Internet reliable data transport for applications wishing to use Internet
Protocol (IP) Multicast services for group data delivery. NORM can also Protocol (IP) Multicast services for group data delivery. NORM can also
support unicast (point-to-point) data communication and may be used for support unicast (point-to-point) data communication and may be used for
such when deemed appropriate. The current NORM protocol specification is such when deemed appropriate. The current NORM protocol specification is
given in the <ulink url="http://www.ietf.org/">Internet Engineering Task given in the <ulink url="https://www.ietf.org/">Internet Engineering Task
Force</ulink> (IETF) <ulink Force</ulink> (IETF) <ulink
url="http://norm.pf.itd.nrl.navy.mil/rfc3940.pdf">RFC 3940</ulink>. This url="https://datatracker.ietf.org/doc/html/rfc5740">RFC 5740</ulink>. This
document is currently a reference guide to the NORM API of the NRL document is currently a reference guide to the NORM API of the NRL
reference implementation. More tutorial material may be include in a reference implementation. More tutorial material may be include in a
future version of this document or a separate developer's tutorial may future version of this document or a separate developer's tutorial may
@ -37,19 +37,19 @@
<title>Background</title> <title>Background</title>
<para>This document describes an application programming interface (API) <para>This document describes an application programming interface (API)
for the <ulink url="http://norm.pf.itd.nrl.navy.mil/">Nack-Oriented for the <ulink url="https://www.nrl.navy.mil/Our-Work/Areas-of-Research/Information-Technology/NCS/NORM/">Nack-Oriented
Reliable Multicast (NORM)</ulink> protocol implementation developed by the Reliable Multicast (NORM)</ulink> protocol implementation developed by the
Protocol Engineering and Advance Networking (<ulink Protocol Engineering and Advance Networking (<ulink
url="http://cs.itd.nrl.navy.mil/">PROTEAN</ulink>) Research Group of the url="https://www.nrl.navy.mil/itd/ncs/">PROTEAN</ulink>) Research Group of the
United States <ulink url="http://www.nrl.navy.mil/">Naval Research United States <ulink url="https://www.nrl.navy.mil/">Naval Research
Laboratory</ulink> (NRL). The NORM protocol provides general purpose Laboratory</ulink> (NRL). The NORM protocol provides general purpose
reliable data transport for applications wishing to use Internet Protocol reliable data transport for applications wishing to use Internet Protocol
(IP) Multicast services for group data delivery. NORM can also support (IP) Multicast services for group data delivery. NORM can also support
unicast (point-to-point) data communication and may be used for such when unicast (point-to-point) data communication and may be used for such when
deemed appropriate. The current NORM protocol specification is given in deemed appropriate. The current NORM protocol specification is given in
the <ulink url="http://www.ietf.org/">Internet Engineering Task the <ulink url="https://www.ietf.org/">Internet Engineering Task
Force</ulink> (IETF) <ulink Force</ulink> (IETF) <ulink
url="http://norm.pf.itd.nrl.navy.mil/rfc5740.pdf">RFC 5740</ulink>.</para> url="https://datatracker.ietf.org/doc/html/rfc5740">RFC 5740</ulink>.</para>
<para>The NORM protocol is designed to provide end-to-end reliable <para>The NORM protocol is designed to provide end-to-end reliable
transport of bulk data objects or streams over generic IP multicast transport of bulk data objects or streams over generic IP multicast
@ -134,7 +134,7 @@
may participate as senders and/or receivers within a NORM session. NORM may participate as senders and/or receivers within a NORM session. NORM
senders transmit data to the session destination address (usually an IP senders transmit data to the session destination address (usually an IP
multicast group) while receivers are notified of incoming data. The NORM multicast group) while receivers are notified of incoming data. The NORM
API provides and event notification scheme to notify the application of API provides an event notification scheme to notify the application of
significant sender and receiver events. There are also a number support significant sender and receiver events. There are also a number support
functions provided for the application to control and monitor its functions provided for the application to control and monitor its
participation within a NORM transport session.</para> participation within a NORM transport session.</para>
@ -159,7 +159,7 @@
linkend="NormCreateInstance"><literal>NormCreateInstance()</literal></link>) linkend="NormCreateInstance"><literal>NormCreateInstance()</literal></link>)
as needed for applications with specific requirements for accessing and as needed for applications with specific requirements for accessing and
controlling participation in multiple <emphasis>NormSessions</emphasis> controlling participation in multiple <emphasis>NormSessions</emphasis>
from separate operating system multiple threads. Or, alternatively, a from separate operating system threads. Or, alternatively, a
single <emphasis>NormInstance</emphasis> could be used, with a "master single <emphasis>NormInstance</emphasis> could be used, with a "master
thread" serving as an intermediary between the <link thread" serving as an intermediary between the <link
linkend="NormGetNextEvent"><literal>NormGetNextEvent()</literal></link> linkend="NormGetNextEvent"><literal>NormGetNextEvent()</literal></link>
@ -194,7 +194,7 @@
number of concurrently active senders, this may translate to significant number of concurrently active senders, this may translate to significant
memory allocation on receiver nodes. Currently, the API allows the memory allocation on receiver nodes. Currently, the API allows the
application to control how much buffer space is allocated for each application to control how much buffer space is allocated for each
active sender (NOTE: In the future, API functions may be provided limit active sender (NOTE: In the future, API functions may be provided to limit
the number of active senders monitored and/or provide the application the number of active senders monitored and/or provide the application
with finer control over receive buffer allocation, perhaps on a per with finer control over receive buffer allocation, perhaps on a per
sender basis).</para> sender basis).</para>
@ -227,7 +227,7 @@
<title>Data Transmission</title> <title>Data Transmission</title>
<para>The behavior of data transport operation is largely placed in <para>The behavior of data transport operation is largely placed in
the control of the NORM sender(s). NORM senders controls their data the control of the NORM sender(s). NORM senders control their data
transmission rate, forward error correction (FEC) encoding settings, transmission rate, forward error correction (FEC) encoding settings,
and parameters controlling feedback from the receiver group. Multiple and parameters controlling feedback from the receiver group. Multiple
senders may operate in a session, each with independent transmission senders may operate in a session, each with independent transmission
@ -253,7 +253,7 @@
be called before any calls to <link be called before any calls to <link
linkend="NormStartReceiver"><literal>NormStartReceiver()</literal></link> linkend="NormStartReceiver"><literal>NormStartReceiver()</literal></link>
are made. However, note that the cache directory may be changed even are made. However, note that the cache directory may be changed even
during active NORM reception. In this case, the new specified during active NORM reception. In this case, the newly specified
directory path will be used for subsequently-received files. Any files directory path will be used for subsequently-received files. Any files
received before a directory path change will remain in the previous received before a directory path change will remain in the previous
cache location. Note that the <link cache location. Note that the <link
@ -477,15 +477,14 @@
Protokit. These are described below.</para> Protokit. These are described below.</para>
<para>The "makefiles" directory contains Unix Makefiles for various <para>The "makefiles" directory contains Unix Makefiles for various
platforms the "win32" and "wince" sub-directories there contain Microsoft platforms. The "win32" and "wince" sub-directories there contain Microsoft
Visual C++ (VC++) and Embedded VC++ project files for building the NORM Visual C++ (VC++) and Embedded VC++ project files for building the NORM
implementation. Additionally, a "waf" (Python-based build tool) build implementation. Additionally, a "waf" (Python-based build tool) build
option is supported that can be used to build and install the NORM library option is supported that can be used to build and install the NORM library
code on the supported platforms. Finally, Python and Java bindings to the code on the supported platforms. Finally, Python and Java bindings to the
NORM API are included and "src/python" and "src/java" directories contain NORM API are included in the "src/python" and "src/java" directories and the
the code for these and the "makefiles/java" directory contains Makefiles "makefiles/java" directory contains Makefiles to build the NORM Java JNI bindings.
to build the NORM Java JNI bindings. Note the "waf" tool can also be used Note the "waf" tool can also be used to build the Java and Python bindings.</para>
to build the Java and Python bindings.</para>
<sect2> <sect2>
<title>Unix Platforms</title> <title>Unix Platforms</title>