[Nfd-dev] question about nrd
Junxiao Shi
shijunxiao at email.arizona.edu
Wed Mar 12 17:30:30 PDT 2014
Logging: trivial code.
Command Interest verification: NRD needs more complex logic such as per-namespace authorization.
Configuration parser: different file format.
If NFD and NRD should be in the same repository because these three modules are shared, same logic would cause NLSR to go into the same repository.
I prefer to keep them separate, because they are different programs.
Yours, Junxiao
Alex Afanasyev <alexander.afanasyev at ucla.edu> wrote:
>I did several iterations of updates in nrd repo, but I still have a
>problem with approving 2 outstanding commits. Neither of them has
>unit tests, but my primary problem is lack of command interest
>verification, which exists now in NFD. It doesn't make sense for me to
>be extremely strict in NFD and yet allow everybody to register prefixes
>using NRD...
>
>Also. After looking more into the code I'm less and less convinced that
>NRD should be in a separate repository. A lot of things have been
>already implemented in NFD (logging, command interest verification,
>config file) and having separate repo basically means that the code
>needs to be copied (and maintained) in two places, instead of one.
>
>How should we proceed?
>
>---
>Alex
>
>
>_______________________________________________
>Nfd-dev mailing list
>Nfd-dev at lists.cs.ucla.edu
>http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140312/eb1b8190/attachment.html>
More information about the Nfd-dev
mailing list