[Ndn-lib] Transport Access From Face

Alex Afanasyev alexander.afanasyev at ucla.edu
Thu Feb 19 10:21:40 PST 2015

> On Feb 19, 2015, at 10:03 AM, Mark Stapp <mjs at cisco.com> wrote:
> just saw this go by:
> On 2/19/15 12:52 PM, Junxiao Shi wrote:
>> Dear folks
> [...]
>> What about an alternative design:
>> struct Reply
>> {
>>   void operator()(const Data& data);
>>   void operator()(const Nack& nack);
>> };
> Can you say something about what a "Nack" is (outside the code, that is)? As you know, it's been a contentious topic, and I'd be interested to know what your current thinking is.

This part is still not fully defined.  So far, the only element that is defined is an application-level nack (= just an ordinary Data packet but with NACK type = name of such data needs to be the same or longer than Interest's name).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-lib/attachments/20150219/0d57d435/attachment.bin>

More information about the Ndn-lib mailing list