<html><head></head><body><p dir=ltr>Logging: trivial code.<br>
Command Interest verification: NRD needs more complex logic such as per-namespace authorization.<br>
Configuration parser: different file format.</p>
<p dir=ltr>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.</p>
<p dir=ltr>I prefer to keep them separate, because they are different programs.</p>
<p dir=ltr>Yours, Junxiao</p>
<br><br><div class="gmail_quote">Alex Afanasyev <alexander.afanasyev@ucla.edu> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">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...<br /><br />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.<br /><br />How should we proceed?<br /><br />---<br />Alex<br /><br /><br /><hr /><br />Nfd-dev mailing list<br />Nfd-dev@lists.cs.ucla.edu<br /><a
href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><br /></pre></blockquote></div></body></html>