<div dir="ltr">Greetings all,<div><br></div><div>If you wish, ignore the last e-mail unless you have a better suggestion than me modifying the Consumer base class... I apologize for e-mailing again so soon, but I did a little digging and found something promising, so I started playing with it. I won't e-mail again this morning (evening? night? I don't even know what time it is...)</div><div><br></div><div>I modified the Consumer class in ndn-consumer.[hpp,cpp] to maintain an extra data member, m_suffix, an uint64. I think added an ".AddAttribute" to the static TypeId definition, so that the helper would allow me to pass "Suffix" as a helper, with UintegerValue as the type.</div><div><br></div><div>Then, in the SendPacket method, I created a condition so that:</div><div><b><br></b></div><div><b> nameWithSequence->appendSequenceNumber(m_suffix) </b></div><div><br></div><div>is used instead of</div><div> nameWithSequence->appendSequenceNumber(seq)</div><div><br></div><div>However, now when I run the application:</div><div><br></div><div>1. It does print out my prefix/suffix in the form /prefix/%FE%<i>suffix</i>?ndn.InterestLifetime=2000&ndn.Nonce=<i>someNonceValue</i></div><div><i><br></i></div><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><br></div><div>3. Was handling this (2, i.e. duplicate removal/prevention) not implemented behind the scenes because the seqNumber always ensured the same item was never requested twice? That seems unrealistic, but I could understand if simply no one got around to it yet.</div><div><br></div><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><br></div><div><br></div><div>Thanks a ton for your patience. I'm learning a lot, but apparently have a long way to go.</div><div><br></div><div>Thanks a ton,</div><div><br></div><div>John</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 12, 2017 at 3:05 AM, John Baugh <span dir="ltr"><<a href="mailto:jpbaugh@umich.edu" target="_blank">jpbaugh@umich.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">Junxiao et al.,<div><br></div><div>Thank you for your response. That does clarify things a bit. Would the best option to, in your words, "program/configure your consumer to send out Interests with same names" be to subclass Consumer (or one of its subclasses) and override one of the methods?</div><div><br></div><div>1. I cannot seem to find where the randomization of the values such as %FE%C3 are being appended to "/prefix/" before the interest is sent. Does anyone know where this would be?</div><div><br></div><div>2. I suppose that my goal is to have a particular Consumer object request say, /prefix/1 multiple times, maybe interspersed with say, prefix/2 or others (but from a finite, reasonably predictable set of options. Thoughts?</div><div><br></div><div>3, I assume if I do (2) even with different Nonces, the producer, cache, etc. will consider anything with /prefix/1 to be a single requested content object, correct? </div><div><br></div><div>4. I would also assume that it's unlikely the Producer would need modified, if you specify that the producer handles "/prefix/" then, anything starting with that should be responded to with content, correct?</div><div><br></div><div>Thanks,</div><div><br></div><div>John</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 6, 2017 at 2:52 PM, 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>Hi John</div><div><br><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br></div><div>When the requested "/prefix" is set for particular consumers, for example, there appear to be many requests made (e.g., ConsumerCbr):</div><div><br></div><div>/prefix/%FE%C3/...</div><div>/prefix/%FE%C4/...</div><div><br></div><div>1. I printed out the contents of cached items in the Content Store (using getFullName().toUri() on the iterator in my loop, starting at begin(), ending at end(), of course.), and noticed that each of these is treated as separate content objects?</div></div></blockquote><div><br></div></span><div>Yes.</div><span><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><br></div><div>2. I was previously under the impression that /prefix/<i>whatever</i> was a single content object, and that the Content Store wouldn't cache more than one of them. Is the /%FE%C3/... part of the content object's true name?</div></div></blockquote><div><br></div></span><div>Yes.</div><span><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><br></div><div>3. If this is the case, it seems like the Consumers never request the same item more than once... is there any way to control this? I want to ultimately simulate multiple requests of the same contents from various consumers to see how it affects the Cs</div></div></blockquote><div><br></div></span><div>You can program/configure your consumer to send out Interests with same names.</div><div><br></div><div>Yours, Junxiao</div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>