Optionally write prefixes to configuration file that were advertised in NLSR
Suggested in ICN. So if NLSR does down and recover then it can load all the prefixes that are supposed to be advertised.
#5 Updated by Saurab Dulal about 1 year ago
Some limitations with this patch.
1. It removes all the comments from the conf file. It's because I am using BOOST to read and write to the conf file, BOOST removes the comments in that process.
2. Once a prefix is advertised without a save command, it cannot be saved later.
3. Once a prefix is withdrawn without a delete command, it will not be deleted from the conf file.
Above limitations has been resolved.
few StatusCodes are introduced in NLSR.
406: Prefix is already saved or deleted from the configuration file.
205: Saving or deleting a prefix from the configuration file. This also includes saving or deleting an already advertised or withdrawn prefix from the configuration file.
StatusCode loosely follows the HTTP semantics described in RFC2616 section 10 (RFC2616)