Feature #4869
closed
Support specifying a different Origin in route registration command
0%
Description
For instance, a producer may want to set origin=65 (client) to enable readvertise-to-nlsr for the prefix being registered.
See https://redmine.named-data.net/projects/nfd/wiki/RibMgmt for the protocol details.
Updated by Anonymous about 5 years ago
Changes are pushed to PyNDN2. In the registerPrefix command, you specify the flags argument. For example, ForwardingFlags().setOrigin(65) . Davide has tested it in Python.
Updated by Anonymous about 5 years ago
Since it now carries more options than just flags, the ForwardingFlags class should be renamed to RegistrationOptions (and may carry more options in the future).
Updated by Anonymous about 5 years ago
Hi Davide. ForwardingFlags is renamed to RegistrationOptions.
https://github.com/named-data/PyNDN2/blob/master/python/pyndn/registration_options.py#L28
Do you want to try it in your code?
Updated by Anonymous about 5 years ago
- Blocks Feature #2576: ForwardingFlags should be removed added
Updated by Anonymous about 5 years ago
Changes are pushed to master in all libraries to rename ForwardingFlags to RegistrationOptions and support getOrigin() in registerPrefix.
Updated by Anonymous about 5 years ago
- Status changed from Feedback to Closed
The CCL API page has been updated.
https://named-data.net/doc/ndn-ccl-api/details/registration-options.html#registrationoptions-setorigin-method
Updated by Davide Pesavento almost 5 years ago
Jeff Thompson wrote:
Hi Davide. ForwardingFlags is renamed to RegistrationOptions.
https://github.com/named-data/PyNDN2/blob/master/python/pyndn/registration_options.py#L28Do you want to try it in your code?
Sorry for the delay. Tried today with PyNDN v2.10beta1-58-g2412131, works fine. Thanks.
There is a typo on the doc page: "Set the child selector"