Activity

From 06/10/2015 to 07/09/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... Anonymous

01:34 PM Feature #3005: Add callback for successful prefix registration: Yes, an integration test sounds good. Anonymous
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? Andrew Brown
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... Anonymous
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 ... Andrew Brown

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:/... Anonymous
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... Anonymous

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... Andrew Brown

10:49 AM Task #2884 (Closed): Deprecate get/setScope, remove in a later release: Changes are merged into the master branch of all client libraries. get/setScope will be removed when task #2624 is cl... Anonymous

08:25 AM Task #2884 (Closed): Deprecate get/setScope, remove in a later release: From the nfd-dev mailing list: "Interest.Scope was was removed from the NDN specification some time ago and we never ... Anonymous

02:14 PM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder: Hi Alex. In note 3, you suggest to throw an exception if the connection is dropped. What should happen for an async p... Anonymous
09:00 AM Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder: I duplicated this thread as a bug at http://redmine.named-data.net/issues/2869. Here is my original post and I'm lean... Andrew Brown

Also available in: Atom

NDN-CCL