[Ndn-lib] wireEncode/wireDecode interface missing in Name class

Burke, Jeff jburke at remap.ucla.edu
Sat Apr 12 07:09:05 PDT 2014


In general we are trying to not expose the application developer to the wire format.  The CCL will shortly provide functions for creating command interests that follow the spec here<http://redmine.named-data.net/projects/nfd/wiki/Command_Interests>.   Are you interested in a different type of command interest structure (requiring you to experiment with the wire format until we can provide library support for such a new structure) or would these  fit your needs?

For Shuo's repo, though it might store things in the wire format, it's unclear to me why the repo would need to understand/parse it directly?    Could you explain more or ask him to email the list with what he is trying to do / needs from the library...


From: Wentao Shang <wentaoshang at gmail.com<mailto:wentaoshang at gmail.com>>
Date: Fri, 11 Apr 2014 19:03:03 -0700
To: "Thompson, Jeff" <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>>
Cc: "ndn-lib at lists.cs.ucla.edu<mailto:ndn-lib at lists.cs.ucla.edu>" <ndn-lib at lists.cs.ucla.edu<mailto:ndn-lib at lists.cs.ucla.edu>>
Subject: Re: [Ndn-lib] wireEncode/wireDecode interface missing in Name class

One example is repo-ng, which stores names in wire format.

Another use case in my mind is that I want to create customized command interest for ndn smart home control, which also requires dealing with wire format names.


On Friday, April 11, 2014, Thompson, Jeff <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>> wrote:
Hi Wentao,

Can you say something more about how your application needs to directly manipulate the Name wire format?

- Jeff T

From: Wentao Shang <wentaoshang at gmail.com<javascript:_e(%7B%7D,'cvml','wentaoshang at gmail.com');>>
Date: Friday, April 11, 2014 5:52 PM
To: NDN Lib <ndn-lib at lists.cs.ucla.edu<javascript:_e(%7B%7D,'cvml','ndn-lib at lists.cs.ucla.edu');>>
Subject: [Ndn-lib] wireEncode/wireDecode interface missing in Name class

Hi all,

In NDN CCL API 0.1a2 documentation, there is no interface to directly manipulate the wire format of Name class. In some applications this feature is needed. And since Name-related operations are essential part of NDN application development, it would be nice in general to have the capability of handling wire format of Names. Any thoughts about adding this interface to the CCL API?




_______________________________________________ Ndn-lib mailing list Ndn-lib at lists.cs.ucla.edu<mailto:Ndn-lib at lists.cs.ucla.edu> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-lib
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-lib/attachments/20140412/c1d18dbe/attachment.html>

More information about the Ndn-lib mailing list