Task #2280
closed
Implement LSDB Dataset Publisher
100%
Description
Implement LSDB DataSet Publisher to publish the LSA information from the LSDB using the defined LSDB DataSet.
Updated by Vince Lehman about 10 years ago
- Subject changed from LSA Publisher to Implement LSDB Dataset Publisher
- Description updated (diff)
Updated by Lan Wang about 10 years ago
- Related to Task #2032: Create specification for NLSR Lsdb dataset added
Updated by Junxiao Shi almost 10 years ago
Design question:
Why is LSDB Status dataset designed to have only one element: the LsdbStatus block?
Why not put AdjacencyLsa, CoordinateLsa, NameLsa directly in the dataset?
Updated by Vince Lehman almost 10 years ago
Junxiao Shi wrote:
Design question:
Why is LSDB Status dataset designed to have only one element: the LsdbStatus block?
Why not put AdjacencyLsa, CoordinateLsa, NameLsa directly in the dataset?
Maybe I am misunderstanding the question, but LsdbStatus, a list of AdjacencyLsas, a list of CoordinateLsas, and a list of NameLsas are all separately retrievable.
/$ROUTER_NAME/lsdb/list
/$ROUTER_NAME/lsdb/adjacencies
/$ROUTER_NAME/lsdb/coordinates
/$ROUTER_NAME/lsdb/names
Did you mean why have the LsdbStatus block at all and instead just directly publish the lists in the dataset?
Updated by Jiewen Tan almost 10 years ago
- Status changed from New to Code review
- % Done changed from 0 to 90
Updated by Alex Afanasyev almost 10 years ago
To implement Junxiao suggestion, you can do something similar to (not the exact code):
Face face;
face.registerPrefix("/$ROUTER_NAME/lsdb/",
[&face] (const Name& prefix) {
face.setInterestFilter(Name(prefix).add("adjacencies"),
onAdjacenciesCallback);
face.setInterestFilter(Name(prefix).add("coordinates"),
onCoordinatesCallback);
...
},
[] (const Name& prefix, const std::string& errMsg) {
... log errors
});
Updated by Vince Lehman over 9 years ago
- Status changed from Code review to Closed
- % Done changed from 90 to 100