[Nfd-dev] LINK support & understanding expected use in apps

[Alex Afanasyev]

Hi Jeff,

We have a minor delay, so we not going to have this in the upcoming minor release (later today).  We will have it a short time after the release and definitely before the next one (either minor or major).

As of right now, we don't yet have a plain text description (we will add it, either as part of NFD developer's guid or as part of ndn-cxx tutorial page) of how to work with link, but we have API documentation (http://named-data.net/doc/ndn-cxx/current/doxygen/d1/d81/classndn_1_1Interest.html#abbf98026d7c36775695ebb038d876bcb, http://named-data.net/doc/ndn-cxx/current/doxygen/d0/d61/classndn_1_1Link.html)
and unit tests (https://github.com/named-data/ndn-cxx/blob/master/tests/unit-tests/link.t.cpp) which can get some idea how to work with it.

---
Alex

> On Aug 31, 2015, at 9:55 AM, Burke, Jeff <jburke at remap.ucla.edu> wrote:
> 
> Hi,
> 
> From a previous NFD call, my understanding was that LINK support in NFD was imminent.  Is it coming in this week's release?
> 
> Also, could someone please suggest the best place to learn about how an application should use LINK as currently designed and implemented?   (Say, for the publisher mobility use case of NDNFit.)  To some extent this can be inferred from the forwarder's use of it and the packet info, but something oriented directly to app developers would be most helpful.
> 
> Thanks!
> Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150831/e630af2f/attachment.bin>