NDN-CCL

05/04/2016

04:17 PM Task #3446 (Closed): NDNLPv2 support

The CCL API page is updated:<br>
http://named-data.net/doc/ndn-ccl-api/face.html#face-expressinterest-methods Anonymous

02:40 PM Task #3446 (Resolved): NDNLPv2 support

The changes are merged to the master branch in all libraries. Anonymous

05/03/2016

08:52 AM Task #3446: NDNLPv2 support

Hi Andrew. Can you send the question to nfd-dev? I think it is general enough and will get more attention. Anonymous

08:23 AM Task #3446: NDNLPv2 support

Question: can I get an example of how someone/anyone has used the different NACK codes to alter the flow of their app... Andrew Brown

05/02/2016

11:37 AM Task #3446 (In Progress): NDNLPv2 support

In the NDNLPv2 branch of jNDN and NDN-JS, added the NetworkNack object and added support for OnNetworkNack to express... Anonymous

04/28/2016

12:08 PM Task #3590 (Closed): MemoryContentCache: Support setInterestFilter

Changes merged to master in all libraries. Anonymous

04/27/2016

03:38 PM Task #3606 (Closed): Set the Interest nonce before saving in the PIT

Changes are committed in all libraries. Anonymous

04/26/2016

09:27 PM Task #3606: Set the Interest nonce before saving in the PIT

Thanks! I'll reply to the email. Anonymous

12:49 PM Task #3606: Set the Interest nonce before saving in the PIT

I asked this in an email to Junxiao, who said:
From protocol point of view, the Nack must be able to locate the co... Anonymous

12:10 PM Task #3606: Set the Interest nonce before saving in the PIT

Just a quick question: Why is it important to compare the nonce of the NACK with the nonce in the PIT? Isn't it enoug... Anonymous

04/25/2016

01:21 PM Task #3606 (Closed): Set the Interest nonce before saving in the PIT

expressInterest makes a copy of the supplied Interest. But currently the nonce is only set when in the wire encoding.... Anonymous

04/22/2016

04:01 PM Task #3446: NDNLPv2 support

Currently, expressInterest has the onData and onTimeout callbacks. To support network Nack, we need another callback.... Anonymous

03:32 PM Task #3446: NDNLPv2 support

Andrew Brown wrote:
> We tried 0.4 but had some startup issues (a BerEncoding exception coming from libcryptopp?) ... Andrew Brown

04/21/2016

11:12 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

Andrew Brown wrote:
> We already have getIsConnected() in there; could we use that?
AsyncTcpTransport.getIsConnec... Anonymous

04/20/2016

04:45 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

But that's on a Transport and you need access to that information at the Node level? Andrew Brown

04:43 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

We already have getIsConnected() in there; could we use that? Andrew Brown

03:12 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

Andrew Brown wrote:
> Jeff Thompson wrote:
> > In the simplest case of a consumer (without register prefix), expres... Anonymous

03:03 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

We need some kind of callback. But the more I think about it, the onNack callback from expressInterest is really supp... Anonymous

02:00 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

Jeff Thompson wrote:
> Perhaps there is a fancier solution using network Nack (which I'm working on implementing i... Andrew Brown

01:56 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

One more comment about that last: if we do reconnect sockets and do re-register prefixes, it seems like there should ... Andrew Brown

01:53 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

Jeff Thompson wrote:
> I agree that something would be better than nothing, but I'll brain dump the concerns I hav... Andrew Brown

01:27 PM Bug #1517 (Closed): registerPrefix adds the onInterest callback even when registration fails

The fix is merged to master in all libraries. Anonymous

04/19/2016

12:08 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

... of course for the case of the consumer, the simplest solution when the application calls expressInterest is where... Anonymous

11:25 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

I agree that something would be better than nothing, but I'll brain dump the concerns I have which have made me procr... Anonymous

10:10 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder

Jeff, I have some new thoughts about this: it seems that option 1 above seems a common enough case that we could add ... Andrew Brown