<div dir="ltr">Junxiao,<br><div><br></div><div>Good call... I was up late so I didn't question what was going on enough. I turns out the printing I was doing was for interests... not the content store contents.</div><div><br></div><div>Now, the only thing in my CS is apparent some setup information, so it appears I have the opposite problem. It doesn't seem to have anything cached by the end of the scenario being run. To print out the content store, I created a method printContentStore that I pass the CS into (that I obtained from the l3protocol for the "router" node in the middle, which I assume is the router...) - and it starts at cs.begin() until cs.end(). I'm using cout and a regular file stream with it, but still - same information, it's not printing anything other than what appears to be setup information.</div><div><br></div><div>In printing, I used the iterator, <b>it</b>, and used code like:</div><div><br></div><div><b>std::cout<<it->getFullName().toUri()<<std::endl;</b></div><div><br></div><div><br></div><div><br></div><div>So I guess the better questions I should be asking are:</div><div><br></div><div>1. <b>When </b>should one print the contents of the content store? After Simulator::Run is called? After Destroy? Before ::Run?</div><div><br></div><div><br></div><div><br></div><div>2. <b>Should I</b> even be trying to print the CS from inside the scenario file at all?</div><div><br></div><div><br></div><div><br></div><div>3. <b>Where </b>should I be printing it, and is there a technique that is preferred over writing your own CS printing routing?</div><div><br></div><div>Thanks,</div><div><br></div><div>John</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 12, 2017 at 7:56 AM, Junxiao Shi <span dir="ltr"><<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi John<br><div><div class="gmail_extra"><br><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>2. The content store still seems to be caching them as separate content items! Even if there are say, 20 different requests for /prefix/%FE%01?... they are each apparently cached separately.</div></div></blockquote></span><div>How do you know that? If you have logs, paste a snippet of relevant logs.<br></div><div>Short logs (less than 200 lines) should be pasted on email body. Long logs should be uploaded to Gist or PasteBin. Do not send logs as attachments.<br></div><div>See also <a href="http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2016-May/001748.html" target="_blank">http://www.lists.cs.ucla.edu/<wbr>pipermail/nfd-dev/2016-May/<wbr>001748.html</a><br></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><b>4. Is ensuring duplicates aren't cached something that the Policy must take care of? (immediately evict an entry with the same /prefix/seqNumber and/or /prefix/suffix ??</b></div></div></blockquote></span>No. Assuming there is only one producer creating the requested Data, subsequent Interests for the same Data should match the existing CS entry and should not be forwarded again.<br></div><div class="gmail_quote">If you are sending multiple Interests with the same name from multiple consumers located in sparse locations, and there are multiple producers, it is possible that each producer can generate a different Data, and those Data could be cached separately. Remember that the Data name ends with an implicit digest, and signing the same name+payload multiple times will generate different signatures and thus different implicit digests, even if those producers are using the same signing key.<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">Yours, Junxiao<br></div></div></div></div>
</blockquote></div><br></div>