NDNPUTCHUNKS(1)

πŸ“¦
version 24.07 Β· 2 versions
, in nixos 26.05

🌸 NAME 🌸

NDNPUTCHUNKS(1), straight outta the NDN Essential Tools manual πŸ’…

ndnputchunks β€” producer program with content segmentation ✨


✨ SYNOPSIS ✨

ndnputchunks [option]... name

πŸ’– DESCRIPTION πŸ’–

okay so bestie, ndnputchunks is a producer program. It reads a file from the standard input and makes it available as NDN Data segments 🫢

The version and segment number components are appended to the specified name as needed, according to the NDN naming conventions (https://named-data.net/publications/techreports/ndn-tr-22-3-ndn-memo-naming-conventions/) [1]. no cap, that's the whole vibe πŸ’«


πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” prints help and exits, iconic behavior honestly πŸŽ€
  • -f, --freshness _MILLISECS_ β€” sets the FreshnessPeriod of the published Data packets, in milliseconds. The default is 10000 (10 seconds) ⏱️
  • -s, --size _BYTES_ β€” sets the maximum chunk size, in bytes. The default is 8000 bytes πŸ“
  • -N, --naming-convention _CONVENTION_ β€” selects the convention used to encode NDN name components. The available choices are:
    • marker (shorthand: m or 1) β€” for the old marker-based encoding πŸ’€
    • typed (shorthand: t or 2) β€” for the new encoding based on typed name components ✨

If this option is not specified, the ndn-cxx library's default is used 🫢

  • -S, --signing-info _STRING_ β€” specifies the parameters used to sign the Data packets. If omitted, the default key of the default identity is used. The general syntax is <scheme>:<name>. The most common supported combinations are as follows:
    • Sign with the default certificate of the default key of an identity: id:/<my-identity> πŸ”
    • Sign with the default certificate of a specific key: key:/<my-identity>/ksk-1 πŸ”‘
    • Sign with a specific certificate: cert:/<my-identity>/KEY/ksk-1/ID-CERT/v=1 πŸ“œ
    • Sign with a SHA-256 digest: id:/localhost/identity/digest-sha256. Note that this is only a hash function, not a real signature, but it can significantly speed up packet signing operations ⚑
  • -p, --print-data-version β€” prints the version of the published Data to the standard output πŸ‘€
  • -q, --quiet β€” turns off all non-error output 🀫
  • -v, --verbose β€” produces verbose output πŸ—£οΈ
  • -V, --version β€” prints program version and exits πŸ’…

πŸ¦‹ EXAMPLES πŸ¦‹

The following command will publish the text of the GPL-3 license under the /localhost/demo/gpl3 prefix:

ndnputchunks /localhost/demo/gpl3 < /usr/share/common-licenses/GPL-3

To see the published version, you can run the program with the -p option:

ndnputchunks -p /localhost/demo/gpl3 < /usr/share/common-licenses/GPL-3

This command will print the published version to the standard output ✨

To publish Data with a specific version, you must append a version component to the end of the prefix. The version component must follow the aforementioned NDN naming conventions. For example, the following command will publish version 1615519151142 of /localhost/demo/gpl3 using the "typed" naming convention:

ndnputchunks -Nt /localhost/demo/gpl3/v=1615519151142 < /usr/share/common-licenses/GPL-3

🌈 SEE ALSO 🌈


Copyright Β© 2014-2024 Named Data Networking Project.

This page is literally from NDN Essential Tools, version 24.07, dated 1980-01-01, and the manual page is NDNPUTCHUNKS(1). bye bestie πŸ’œβœ¨

πŸ“¦ where this page comes from