Optional
announcement?: FwFace.RouteAnnouncementWhat name to be readvertised.
Ignored if prefix is undefined
.
Optional
autoWhether to add handler return value to .dataBuffer
.
This is only relevant when .dataBuffer
is set. If true
, when the ProducerHandler
returns a Data packet, it is automatically inserted to the DataBuffer.
Optional
concurrency?: numberHow many Interests to process in parallel.
Optional
dataOutgoing Data buffer.
Providing an outgoing Data buffer allows the ProducerHandler to prepare multiple Data packets in response to one Interest, in which one Data satisfies the current Interest and additional Data satisfy upcoming Interests. This is useful for a producer that generates a multi-segment response triggered by a single Interest, such as a StatusDataset producer in NFD Management protocol.
The producer handler can prepare the Data packets and insert them to the DataBuffer. Either it
can return undefined
, so that the DataBuffer is queried with the current Interest and the
first matching Data is sent. Or it can return a specific Data packet for satisfying the
current Interest.
Optional
dataIf specified, automatically sign Data packets that are not yet signed.
If the ProducerHandler returns a Data packet that is not signed (its SigType is Null), it is automatically signed with this signer.
This option does not apply to Data packets manually inserted into .dataBuffer
. To auto-sign
those packet, specify DataStoreBuffer.Options.dataSigner in addition.
Optional
describe?: stringDescription for debugging purpose.
Logical forwarder instance.
Optional
modifyModify Interest according to specified options.
Optional
retx?: RetxPolicyRetransmission policy.
Optional
routeWhether routes registered by producer would cause @ndn/fw
internal FIB to stop matching
toward shorter prefixes.
Optional
signal?: AbortSignalAbortSignal that allows cancelation via AbortController.
Optional
verifier?: VerifierData verifier.
Delete packet(s).
Insert packet(s).
Client to interact with ndn-python-repo.