Actions
Bug #1047
open
The removeRegisteredPrefix API should "unregister" from the forwarding daemon
Status:
New
Priority:
Normal
Assignee:
-
Start date:
10/01/2013
Due date:
% Done:
0%
Estimated time:
Description
The registerPrefix method returns an ID so that removeRegisteredPrefix can remove the entry in the local registered prefix table. But this only means that the library will ignore incoming interests which are still sent by the forwarding daemon. How to reverse the register process and "unregister" from the forwarding daemon?
http://named-data.net/codebase/platform/documentation/ndn-ccl-api/#FaceremoveRegisteredPrefix_Method
Updated by Anonymous over 9 years ago
- Project changed from 4 to NDN-CCL
- Subject changed from RemoveRegisteredPrefix should "unregister" from the forwarding daemon to The removeRegisteredPrefix API should "unregister" from the forwarding daemon
Updated by Anonymous over 9 years ago
Need to add optional callbacks for success and failure.
Updated by
Updated by Anonymous over 8 years ago
- Related to Feature #2075: The library should have an API to inform the application when the connection is lost to the forwarder added
Updated by Junxiao Shi over 7 years ago
How to reverse the register process and "unregister" from the forwarding daemon?
The library should invoke RibMgmt rib/unregister command to inform the forwarding daemon.
Actions