[Ndn-interest] NDN chunk

[Marzieh Babaeianjelodar]

Ok. Now I have another question about this part of the documentation:

When I run the following command two times, and I give the second time the old specific version %FD%00%00%01Z%82%AF%A4%EF , with the ndncatchunks I still get the latest version. I mean what is this command good for? Why do we need to publish an old version data again when we can just retrieve it with ndncatchunks -d fixed?

I hope you understood my question  

To publish data with a specific version, you must append a version component to the end of the prefix. The version component must follow the aforementioned NDN naming conventions. For example, the following command will publish the version %FD%00%00%01Qc%CF%17v of the /localhost/demo/gpl3 prefix:

ndnputchunks ndn:/localhost/demo/gpl3/%FD%00%00%01Qc%CF%17v < /usr/share/common-licenses/GPL-3


> On Feb 27, 2017, at 9:48 PM, Marzieh Babaeianjelodar <babaeim at clarkson.edu> wrote:
> 
> Ok I think I got my answer to that question. We can get it through "-d fixed”.
> 
>> On Feb 27, 2017, at 9:22 PM, Marzieh Babaeianjelodar <babaeim at clarkson.edu <mailto:babaeim at clarkson.edu>> wrote:
>> 
>> Thanks it was very helpful.
>> 
>> I have another question. What if we change the file and update it and we want to retrieve the old file with an older version? Can we just run the command with the version name?
>> 
>>> On Feb 27, 2017, at 8:13 PM, Nick Briggs <nicholas.h.briggs at gmail.com <mailto:nicholas.h.briggs at gmail.com>> wrote:
>>> 
>>> Run "ndncatchunks -h" for the help text... most of the tools have -h or --help options.
>>> 
>>> From the help for ndncatchunks --
>>> 	"-d" does version discovery and takes argument "fixed" or "iterative".
>>> 	"-v" turns on verbose output but doesn't affect the NDN packets sent vs. not having "-v".
>>> Each time  you publish data with ndnputchunks it will create a new version -- the new version number is what gets printed with the "-p" option.  The individual packets that compose what you think of as a "file" are going to be named as (using your example below)
>>> 	/localhost/demo/gpl3/<version#>/<chunk #>
>>> where the version and chunk components are binary coded (plus a leading marker) representations of the values.
>>> 
>>> Look at the documentation (or look at the source for the command line parsing...) for how to turn on packet logging for the NDN forwarding daemon -- then you can see exactly what's going on at the packet level when you run ndnputchunks/ndncatchunks (or any other NDN command that's talking to the forwarding daemon)
>>> 
>>> -- Nick Briggs
>>> 
>>> 
>>>> On Feb 27, 2017, at 4:55 PM, Marzieh Babaeianjelodar <babaeim at clarkson.EDU <mailto:babaeim at clarkson.edu>> wrote:
>>>> 
>>>> What is the difference between these two commands:
>>>> ndncatchunks -d iterative ndn:/localhost/demo/gpl3
>>>> 
>>>> ndncatchunks -v ndn:/localhost/demo/gpl3
>>>> 
>>>> _______________________________________________
>>>> Ndn-interest mailing list
>>>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest <http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest>
>>> 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170227/e69bde2c/attachment-0001.html>