Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Researcher

You want to observe what the engine does, measure it, and wire engines together for experiments. The instrument surface lets you tap every packet and inject behaviour without changing the engine — it is opt-in and looser than the application or extension APIs by design.

Assumes One packet, six depths: you are here to watch and measure that pipeline, not just use it.

Extension extension The instrument tier is gated behind the experimental-instrument feature and is not part of any NDN community spec — it is an ndn-rs research surface. Expect a looser stability promise than Develop or Extend.
Your first win Attach a TapFace and watch every packet cross it. → Instrument tier.

Where to stop

The instrument tier is for measurement and experiments, not production data paths. If your tap is shaping real traffic rather than observing it, you have crossed into the Extender path (a Strategy or Face), which carries a firmer contract.

The path

  1. Instrument tierTapFace, packet observation, wiring two engines.
  2. Interest and Data lifecycle — the pipeline you are measuring.
  3. Performance — throughput knobs and how to benchmark.