How many chunks ahead of latest request to store in buffer. This is ignored if the ChunkSource supports getChunk() function.
A larger number can reduce latency of fulfilling Interests if ChunkSource is slow. A smaller number reduces memory usage.
How many chunks behind latest request to store in buffer. This is ignored if the ChunkSource supports getChunk() function.
After processing an Interest requesting segment
i, subsequent Interests requesting
i - bufferBehind cannot be answered.
A larger number or even
Infinity allows answering Interests requesting early segments,
at the cost of buffering many generated packets in memory.
A smaller number reduces memory usage, at the risk of not being able to answer some Interests,
which would become a problem in the presence of multiple consumers.
Data FreshnessPeriod (in milliseconds).
Choose a segment number naming convention. Default is Segment from @ndn/naming-convention2 package.
A private key to sign Data. Default is SHA256 digest.
Generated using TypeDoc