Task #1807
closed
nfd-status should include some identification of NFD
Added by Alex Afanasyev over 10 years ago.
Updated over 10 years ago.
Description
Both plain text and XML output should include some kind of identification of NFD instance. This could be KeyLocator information (e.g., key name) or something else from Data packets.
- Status changed from New to In Progress
- Assignee set to Chengyu Fan
- Target version set to v0.2
- Start date deleted (
07/28/2014)
I suggest displaying the KeyLocator field, together with version information; this means, such information is not displayed in plain text if version is not requested.
The KeyLocator field is likely to contain a Name, but the code should be prepared to handle a KeyDigest.
This Task requires no change in ForwarderStatus protocol.
The general status contains the version information as well. Why not put the nfd id in the general status? Especially if we need to show it on the status page.
For the KeyLocator field handling, that's a good suggestion.
General NFD status:
routerKey=/example/router/ucla/spurs
version=2000
startTime=20140725T232341.374000
currentTime=20140725T233240
uptime=538 seconds
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF