Task #1312
closedTask #1308: Strategy choice and dispatch
nfdc: strategy-choice
100%
Updated by Junxiao Shi almost 11 years ago
- Due date deleted (
03/02/2014) - Start date deleted (
03/02/2014)
Updated by Hila Ben Abraham almost 11 years ago
Updated by Junxiao Shi almost 11 years ago
#1312 is the consumer, #1311 is the producer.
Development for both can start when protocol (#1310) is completed.
In 1970s, it's common to write programs for a machine that is not yet manufactured.
Both machine and programs follow the documentation, so they will work once the machine is released.
Similarly, both producer and consumer follow StrategyChoice protocol, and they will work.
For task #1312 and #1311, end-to-end testing is possible only when both tasks have some code.
Individually testing #1312 is still possible: don't run NFD, but use netcat to listen on the NFD's socket.
netcat would capture what nfdc writes into the socket, and the written octets can be inspected to determine whether consumer conforms to the protocol.
Updated by Hila Ben Abraham almost 11 years ago
- Status changed from New to In Progress
Updated by Hila Ben Abraham almost 11 years ago
- % Done changed from 0 to 100
I'm about to submit 2 commits: one for nfd (including nfdc changes) and one for ndn_cpp_dev (including the StrategyChoiceManagementOptions).
Should I also delete strategy field from FibManagementOptions?
Updated by Alex Afanasyev almost 11 years ago
Ehm... I thought we agreed to unify "options" data structure? At least in here we could just reuse the existing FibMangementOptions...
Updated by Junxiao Shi almost 11 years ago
Alex Afanasyev wrote:
Ehm... I thought we agreed to unify "options" data structure? At least in here we could just reuse the existing FibMangementOptions...
I plan not only to unify Options
, but also combine all management protocols into one. I'll send the proposal sometime.
Updated by Alex Afanasyev almost 11 years ago
Got it. But what should we do for this one? Reuse FibManagementOptions, create new options as per-spec, or wait till spec update?
Updated by Junxiao Shi almost 11 years ago
We should create new one for now. FibManagementOptions
and StrategyChoiceOptions
have different TLV-TYPE numbers, so FibManagementOptions
cannot be reused.
Spec update will not happen very soon.
Updated by Alex Afanasyev almost 11 years ago
Ok. Hila, go ahead with the push. I would not modify anything with FibManagementOptions, since we are going to change it in the future anyways.
Updated by Hila Ben Abraham almost 11 years ago
- Status changed from In Progress to Closed