[Ndn-interest] Fixed window size for interests in ndnfs or PyNDN like ndncatchunks

Ishita Dasgupta ishita.dasgupta at gmail.com
Tue Aug 15 09:35:03 PDT 2017

Hi Jeff,

Any instruction doc to install PyCNL? I tried running Makefile in the doc
section that throwed what I'm assuming dependency not installed exceptions.


On Fri, Jul 28, 2017 at 11:38 AM, Thompson, Jeff <jefft0 at remap.ucla.edu>

> Hello Ishita,
> In the following project, we implemented a SegmentStream which sends
> multiple interest for segments and assembles the received segments in
> order. Here is the method which responds to receiving a new segment:
> https://github.com/named-data/PyCNL/blob/master/python/pycnl
> /segment_stream.py#L140
> It uses a utility class which represents the names in a namespace (like
> the names of segments) and keeps track of whether an interest was sent and
> the content of the received data packet.
> https://github.com/named-data/PyCNL/blob/master/python/pycnl
> /namespace.py#L32
> Here is an example from that project that uses the utility to fetch a file
> from memoria.ndn.ucla.edu which is running NDNFS.
> https://github.com/named-data/PyCNL/blob/master/examples/tes
> t_segmented.py#L36
> To optimize interest pipeline often depends on the application. For
> example, the NDN RTC (video streaming) has code to adjust the number of
> interest based on the video rate, etc.
> Thanks,
> - Jeff T
> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of
> Ishita Dasgupta <ishita.dasgupta at gmail.com>
> Date: Friday, July 28, 2017 at 0:47:00
> To: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
> Subject: [Ndn-interest] Fixed window size for interests in ndnfs or PyNDN
> like ndncatchunks
> Hi All,
> Has anyone implemented the fixing of a window size for interest packet
> requests (rather than having one interest sent out per data packet
> sequentially, as is the case in ndnfs and PyNDN) like in ndncatchunks?
> The ndnfs paper mentions having implemented a fixed-size pipeline
> mechanism in their paper, but I was unable to find any such ndnfs client on
> the ndnfs-port github repo. It would be great if someone has any
> information regarding this and can point me to any relevant information.
> Thanks,
> Ishita
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170815/ae918864/attachment.html>

More information about the Ndn-interest mailing list