Additional projects

NUM8-LUP

Small NUM8 changes need reliable propagation over constrained and unreliable links.

Legacy batch and recommended async sender/receiver protocols encode ADD/REMOVE operations, acknowledgements and retransmissions.

DevelopmentMITC99
GitHubQuick Start
Last verified
Not audited against current README/docs
Platform scope
Portable C99; integration depends on caller-provided adapters

What it solves

Small NUM8 changes need reliable propagation over constrained and unreliable links.

How it works

1NUM8 operation log→2sender→3constrained transport→4receiver→5apply callback

Use it when

Propagate a small identifier-set delta
Track progress independently per receiver
Request only the next missing operation after restart

Quick Start

#include "num8lora_sender.h"
#include "num8lora_receiver.h"
/* Initialize the async sender/receiver and exchange BEACON, DATA and ACK/NACK frames. */

Engineering evidence

  • Public headers, implementations, examples, protocol docs and tests are present

Known limits

  • Designed for small infrequent changes rather than throughput
  • Transport is supplied externally
  • Legacy and async protocol lines must not be confused