[Nfd-dev] Intended scope of client.conf

[Burke, Jeff]

There are no changes required for NFD.   We are going to implement client support in NDN-CCL based on the examples available for now, but think that a spec document is important eventually if all applications are supposed to use this file for their default configuration in talking to the forwarder.

A separate but related issue is that instructions need to be provided for how to get nfd/nrd running properly under a specific user (say, ndn)  as Alex and others have indicated is the correct way to run it.  This is done under the package installations but not detailed for those building from source.

Jeff

From: "Lan Wang (lanwang)" <lanwang at memphis.edu<mailto:lanwang at memphis.edu>>
Date: Fri, 22 Aug 2014 14:48:18 +0000
To: Jeff Burke <jburke at remap.ucla.edu<mailto:jburke at remap.ucla.edu>>
Cc: "<nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>" <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>
Subject: Re: [Nfd-dev] Intended scope of client.conf

Any conclusion on this issue?  Are there any changes necessary for nrd?

Lan
On Aug 18, 2014, at 3:25 PM, "Burke, Jeff" <jburke at remap.ucla.edu<mailto:jburke at remap.ucla.edu>> wrote:


Hi folks,

Is there any specification for the purpose and scope of client.conf.  E.g., how it can be located, what can be specified there, and what code should pay attention to it?

We need to consider how to handle this specification in the NDN-CCL libraries, and would prefer to work from a design specification rather than existing code in ndn-cxx.   For code like ndn-js, it may not always apply, so we need to understand defaults and assumptions, too.

Please see:
http://redmine.named-data.net/issues/1850

Thanks,
Jeff

_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto: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/20140822/d7809f75/attachment.html>