NFD » ndn-tools

For ndnpeek, it could simply print the incoming Nack, and exit with a code that differs from Data and timeout.

The Nack should be printed as LpPacket wire encoding to stdout (rather than stderr) so that it can be processed by a script (e.g. with ndn-dissect).

20151015 conference call rejects note-1 design, because LpPacket is at a lower layer than Data.

Instead, the following design is approved:

• Without -p option, the Nack header field should be printed as wire encoding to stdout.
• With -p option, the NackReason code should be printed to stdout.

I tried to use the Face::expressInterest that handles nack, and implement the onNack() method to satisfy note-2. The problem was that the following call couldn't find a matching member function. What's the right way to call?

m_face.expressInterest(createInterestPacket(),
                                          
bind(&NdnPeek::onData, this, _1, _2),
                                          
bind(&NdnPeek::onNack, this, _1, _2),
                                          
bind(&NdnPeek::onTimeout, this, _1));
                                          

Teng Liang wrote:

To test the change, the attached file is performed as the producer replies to any Interests with a NACK .

Can you write a unit test instead?

Davide Pesavento wrote:

Can you write a unit test instead?

Currently, ndn-peek.cpp has the symbol _main inside. How about I do a separate commit (or issue) for the unit test?

Unit tests should be added in #3558. It can be performed either before or after this issue.