[Ndn-lib] wireEncode/wireDecode interface missing in Name class
jburke at remap.ucla.edu
Sat Apr 12 07:12:41 PDT 2014
Yes, the goal is to provide wire format independent APIs to application developers. This is the current approach of the "common client libraries." (As a sort of proof of concept, we can change between binary xml and tlv in the ndnrtc application with no change to the app, though there are some differences between the fields/structure in the two formats that don't make this something we intend to do regularly.)
From: "Dave Oran (oran)" <oran at cisco.com<mailto:oran at cisco.com>>
Date: Sat, 12 Apr 2014 12:17:09 +0000
To: Wentao Shang <wentaoshang at gmail.com<mailto:wentaoshang at gmail.com>>
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
This is fairly scary. What if we decide to change the wire format? Do all the applications break?
Maybe we're just having a terminology misunderstanding here. Applications should have an API that allows them to construct and deconstruct names from/to typed name components. It's the protocol stack's responsibility to take those application-oriented data structures and marshall/unmarshall the wire format of the name field in the messages.
If such an API doesn't exist that's a major hole, IMO.
On Apr 11, 2014, at 10:03 PM, "Wentao Shang" <wentaoshang at gmail.com<mailto:wentaoshang at gmail.com>> wrote:
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:
Can you say something more about how your application needs to directly manipulate the Name wire format?
- Jeff T
Date: Friday, April 11, 2014 5:52 PM
Subject: [Ndn-lib] wireEncode/wireDecode interface missing in Name class
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?
PhD @ IRL, CSD, UCLA
PhD @ IRL, CSD, UCLA
Ndn-lib mailing list
Ndn-lib at lists.cs.ucla.edu<mailto:Ndn-lib at lists.cs.ucla.edu>
_______________________________________________ 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...
More information about the Ndn-lib