Getting the stored content information inside the cache replacement policy

[subodhpd]

I would like to use the information of the content inside the cache replacement policy such as:

1)Time of generation(by the producer) of contents present in the content store.
2)Number of requests of the contents present in the content store.
3)Time at which the contents are cached in the content store.
4)Time of last request of the contents in the content store
please help me getting these information

[adiparamartha]

Hello @subodhpd, thank you for visiting my work.

Based on your problem, I can observe that you might need to add specific time for each content requested and processed. Actually, I have never done that before, but I have some suggestions that you might be able to follow:

1. Take a look into my paperwork that explains how the LRFU replacement policy is built with ndnsim in the NS3 environment
   Paper 2
   Paper 1

2. As far as I know, to add time constraint information in NDN, you need to modify the time module that comes from NS3 and use it in your replacement policy code.

3. While modifying your replacement policy, you can add the time information for each content entered, referenced, or removed from the Content Store. Therefore, you can use it for your replacement policy info.

4. I strongly suggest fixing the problem one-by-one until you fully understand how the NDN replacement policy work in ndnsim.

Hopefully, it can help you,
Thank you

[subodhpd]

Dear Sir Thank you so much for the reply. First of all, I'm really sorry for the late reply. Actually I have been reading your paper and the replacement strategy code given in ndnSIM 2.8(Ubuntu 20.04). Surely once i will go through the paper fully, I will share my doubts and difficulties with you regarding the code and your paper as well.

…

On Mon, Mar 14, 2022 at 10:12 AM Made Adi Paramartha Putra < ***@***.***> wrote: Hello @subodhpd <https://github.com/subodhpd>, thank you for visiting my work. Based on your problem, I can observe that you might need to add specific time for each content requested and processed. Actually, I have never done that before, but I have some suggestions that you might be able to follow: 1. Take a look into my paperwork that explains how the LRFU replacement policy is built with ndnsim in the NS3 environment Paper 2 <https://ieeexplore.ieee.org/abstract/document/8988828> Paper 1 <https://ieeexplore.ieee.org/abstract/document/8978218> 2. As far as I know, to add time constraint information in NDN, you need to modify the time module that comes from NS3 and use it in your replacement policy code. 3. While modifying your replacement policy, you can add the time information for each content entered, referenced, or removed from the Content Store. Therefore, you can use it for your replacement policy info. 4. I strongly suggest fixing the problem one-by-one until you fully understand how the NDN replacement policy work in ndnsim. Hopefully, it can help you, Thank you — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASR3UZVPL5B4OAO2NJBTQ23U727T5ANCNFSM5QOZ24GA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: <adiparamartha/LRFU-Replacement-Policy-using-ndnSIM/issues/2/1066335695@ github.com>

-- Thanks & Regards, Subodh Mishra