Task #1128: mock implementation of PIT - NFD - NDN project issue tracking system

Task #1128

closed

mock implementation of PIT

Added by Junxiao Shi almost 11 years ago. Updated over 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Junxiao Shi

Category:

Tables

Target version:

Mock

Start date:

Due date:

01/26/2014

% Done:

100%

Estimated time:

5.00 h

Description

Implement a subset of PIT entry and PIT table functionality.

Pit class contains: insert, findAllDataMatches, remove

pit::Entry` class contains: getInterest, getName, getInRecords, getOutRecords, isNonceSeen, insertOrUpdateInRecord, deleteInRecords, insertOrUpdateOutRecord, deleteOutRecord

There is no performance requirement on this mock implementation.

Related issues 2 (0 open — 2 closed)

Blocked by NFD - Task #1148: mock implementation of time structs

Closed

Junxiao Shi

01/24/2014

Actions

Precedes NFD - Task #1139: mock forwarder initialization

Closed

01/27/2014

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Junxiao Shi almost 11 years ago

Assignee set to Junxiao Shi
Start date changed from 01/23/2014 to 01/24/2014

Actions

Copy link

Updated by Junxiao Shi almost 11 years ago

Due date changed from 01/27/2014 to 01/25/2014
Start date deleted (~~01/26/2014~~)

Actions

Copy link

Updated by Junxiao Shi almost 11 years ago

Status changed from New to In Progress

Actions

Copy link

Updated by Alex Afanasyev almost 11 years ago

Target version set to Mock

Actions

Copy link

Updated by Junxiao Shi almost 11 years ago

Due date changed from 01/25/2014 to 01/26/2014

Actions

Copy link

Updated by Junxiao Shi almost 11 years ago

I need clarification on API:

Should fib::Entry::insertOrUpdateInRecord update lastNonce, lastRenewed, expiry fields in InRecord, or should the caller (forwarding) do it?
Should fib::Entry::insertOrUpdateOutRecord update lastNonce, lastRenewed, expiry, isPending fields in OutRecord, or should the caller (forwarding) do it?
What API should forwarding use to set isPending of OutRecord to false?

Actions

Copy link

Updated by Alex Afanasyev almost 11 years ago

I need clarification on API:

Should fib::Entry::insertOrUpdateInRecord update lastNonce, lastRenewed, expiry fields in InRecord, or should the caller (forwarding) do it?

The call has all necessary information (it is being passed reference to Interest), so it should do it itself.

Should fib::Entry::insertOrUpdateOutRecord update lastNonce, lastRenewed, expiry, isPending fields in OutRecord, or should the caller (forwarding) do it?

Same thing. I would say it should do it.

What API should forwarding use to set isPending of OutRecord to false?

Good question. I again blanking on why we have it here. Isn't it supposed to be pending whenever OutRecord exists?

Actions

Copy link

Updated by Junxiao Shi almost 11 years ago

Alex Afanasyev wrote:

What API should forwarding use to set isPending of OutRecord to false?

Good question. I again blanking on why we have it here. Isn't it supposed to be pending whenever OutRecord exists?

Yes, isPending is unnecessary since Nonces are stored in m_nonces field.
There should be a pit::Entry::deleteOutRecord method.

Actions

Copy link