Task #1128
closed
mock implementation of PIT
Added by Junxiao Shi over 10 years ago.
Updated about 10 years ago.
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.
- Assignee set to Junxiao Shi
- Start date changed from 01/23/2014 to 01/24/2014
- Due date changed from 01/27/2014 to 01/25/2014
- Start date deleted (
01/26/2014)
- Status changed from New to In Progress
- Target version set to Mock
- Due date changed from 01/25/2014 to 01/26/2014
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?
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?
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.
- Description updated (diff)
- Status changed from In Progress to Code review
- % Done changed from 0 to 100
- Status changed from Code review to Closed
- Description updated (diff)
Also available in: Atom
PDF
Updated by 
Updated by