App author
You want to fetch and publish named data from your own program. You do not need to run a forwarder, write a strategy, or learn the engine internals — you need a client API and a trust policy. This page is the shortest line to a working app.
Assumes the one idea from Why NDN is different: you fetch a name, and what comes back is signed.
Your first win
Connect a
Consumer and call fetch_object to pull
a Data by name. → Five-minute app.
Publishing the other side is the ten-minute producer.
Where to stop
You can build a complete application without ever touching the forwarder’s internals.
You do not need
the PIT/FIB/Content Store internals, forwarding strategies, face types,
or routing. Those are the Extender path. The one
thing you do own is your trust policy — decide it deliberately:
Trust, first.
The path
- Five-minute app — fetch a
Databy name. - Ten-minute producer — serve one.
- Trust, first — choose the policy that decides what you accept.
- Building an application — the fuller walkthrough.
- Develop tier — the stable API surface, as reference.