[Nfd-dev] [EXT] latest nfd commit breaks mini-ndn

[Junxiao Shi]

Hi Nikos

See https://redmine.named-data.net/issues/5304 for the technical reason
behind changing socket path.
To reduce manpower, it was decided to perform a breaking change.

Yours, Junxiao

On Thu, Jan 11, 2024, 18:16 Nikos Fotiou via Nfd-dev <
nfd-dev at lists.cs.ucla.edu> wrote:

> *External Email*
>
> Hi,
>
> This commit
> https://github.com/named-data/NFD/commit/4c95771bd1b0e9c26a2e6817f4a3b2e814697f04
> breaks mini-ndn as it assumes that the socket file is in another location
> (in this line here
> https://github.com/named-data/mini-ndn/blob/9665f5c9c1dd6f55f9c456c51e68959f9a33d5af/minindn/apps/nfd.py#L38
> ).
>
> I am wondering, why the socket path had to change?
>
> Best,
>
> Nikos
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> https://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/20240111/36eccd7c/attachment.html>