You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.
We should add a FecSocket for ARDOP's unconnected, forward error-correction mode of operation. FEC is very similar to UDP, except that packets may be repeated. FEC frames may also be co-mingled with ID frames.
The biggest hurdle is the need to specify the FECMODE. The available modulation modes change with every major release of ARDOP. We can either:
Tie our public API to ARDOP major versions; OR
Abstract the mode selection process out somewhat.
In general, (1) is the choice with the simpler implementation, and it is probably the correct one.
The text was updated successfully, but these errors were encountered:
We should add a
FecSocket
for ARDOP's unconnected, forward error-correction mode of operation. FEC is very similar to UDP, except that packets may be repeated. FEC frames may also be co-mingled with ID frames.The biggest hurdle is the need to specify the
FECMODE
. The available modulation modes change with every major release of ARDOP. We can either:In general, (1) is the choice with the simpler implementation, and it is probably the correct one.
The text was updated successfully, but these errors were encountered: