Activity
From 06/28/2015 to 07/27/2015
07/24/2015
- 03:45 AM Task #3068 (Abandoned): Update to ndn-cxx semantics for setDefaultIdentity, setDefaultKeyNameForIdentity and setDefaultCertificateNameForKey
- In ndn-cxx sec-public-info, the semantics of the API for setDefaultIdentity, setDefaultKeyNameForIdentity and setDefa...
07/08/2015
- 10:56 AM Feature #3005 (Closed): Add callback for successful prefix registration
- The changes are merged into branch issue/2565-async-IO. I needed to merged because we will make further changes to No...
07/07/2015
- 01:34 PM Feature #3005: Add callback for successful prefix registration
- Yes, an integration test sounds good.
- 12:36 PM Feature #3005: Add callback for successful prefix registration
- Tested it out and it works great. I wrote an integration test; would you like to add it?
- 11:15 AM Feature #3005: Add callback for successful prefix registration
- Done. Give it a try in branch issue/3005-OnRegisterSuccess.<br>
https://github.com/named-data/jndn/blob/issue/3005-O... - 10:52 AM Feature #3005: Add callback for successful prefix registration
- I think having the IDs would be useful for me, at least. For example, to clean up my registered prefixes I store the ...
07/06/2015
- 01:42 PM Feature #3005 (In Progress): Add callback for successful prefix registration
- Hi Andrew. Please try branch issue/3005-OnRegisterSuccess (which is branched from issue/2565-async-IO). <br>
https:/... - 11:54 AM Feature #3005: Add callback for successful prefix registration
- The register success callback in ndn-cxx just passes the prefix name. But there is also the registeredPrefixId. Is th...
07/02/2015
- 01:31 PM Feature #3005 (Closed): Add callback for successful prefix registration
- If my application registers a prefix on face A and immediately sends an interest to it on face B, the interest will f...
Also available in: Atom