RIB dataset publisher
Develop a publisher of RIB dataset.
#11 Updated by Alex Afanasyev about 5 years ago
As of right now, you will not be able to use segment publisher at all (since it is part of daemon/).
One option is to move it to
core/ and make templated, so it can be used with AppFace (in NFD internally) and anywhere else with ndn::Face. Junxiao, does this sound reasonable or we should do something else?
#13 Updated by Anonymous about 5 years ago
No objection to moving SegmentPublisher to core, but it relies on AppFace because SegmentPublisher::publishSegment calls AppFace::sign (only AppFaces have an associated keychain). If you want it to use a generic Face, then you will need provide the keychain some other way.
#15 Updated by Anonymous about 5 years ago
That may be an option. I think the current implementation was part of the effort to avoid global things to help future porting to ndnsim. Just keep in mind that some management things will also need corresponding tweaks:
- ManagerBase::sendResponse (2 args)
- NotificationStream::postNotification (should this also be moved to core?)
#18 Updated by Junxiao Shi about 5 years ago
I disagree with having a global
I also withdraw the agreement with note-11.
It's okay to have a global Scheduler, because it deals with relative time only, which is same across nodes (unless we model hardware clock drift which is generally invisible).
It's unacceptable to have a global key chain, because the possession of keys on different nodes are different.
SegmentPublisher with both
AppFaceBase, abstract sending and receiving to
AppFaceBaseconstructor takes a
KeyChain, and can sign Data with the KeyChain (or simply has a
- create a new
AppFaceclass which derives from
AppFaceBase; its constructor takes
KeyChain, and passes the
KeyChainto base class constructor, but uses the
ndn::Facefor sending and receiving