[Nfd-dev] ndncatchunks3 and ndnputchunks

[Steve DiBenedetto]

I would prefer to keep these applications as examples and improve them to conform to best practices. In general, the more examples of how to use the library, the better.

You can assign the ndn-cxx task (if any) to me.

-Steve

> On Oct 21, 2014, at 11:39 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> 
> Hi Alex
> 
> I think they shall be deleted.
> 
> ndncatchunks3 fetches segments continuously until there's a timeout, then claims it's done.
> It doesn't allow version segment, and doesn't recognize FinalBlockId.
> If pipelining is enabled, the segments could be printed in wrong order.
> This shouldn't become an example because it doesn't reflect the best practices.
> 
> This pair of tools could be only useful as traffic generators, but we already have a real traffic generator.
> 
> Yours, Junxiao
> 
> On Tue, Oct 21, 2014 at 12:58 PM, Alex Afanasyev <alexander.afanasyev at ucla.edu <mailto:alexander.afanasyev at ucla.edu>> wrote:
> They originally meant to be simple debug tools / examples.  They probably can be removed or demoted to examples category (and moved to examples/ folder).
> 
> ---
> Alex
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://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/20141022/3d2f6de6/attachment.html>