Feature #1794
closedMake KeyChain use PIB Service
0%
Description
Implement SecPublicInfo interface to use PIB service. The new class name is SecPublicInfoService
.
Updated by Junxiao Shi about 10 years ago
- Start date deleted (
07/23/2014)
SecPublicInfo
has a synchronized API.
To use the PIB service as a backend, an asynchronized API is needed to avoid blocking the caller for long periods of time.
Updated by Alex Afanasyev over 9 years ago
- Related to Task #2554: PIB service added
Updated by Junxiao Shi over 9 years ago
- Blocked by Feature #1529: PIB service added
Updated by Junxiao Shi over 9 years ago
- Target version changed from v0.3 to v0.4
Pib
and PibImpl
(#2451) intend to replace SecPublicInfo
. Should this be implemented as a subclass of PibImpl
instead?
The problem in note-1 is still applicable.
Updated by Junxiao Shi over 9 years ago
At 20150803 conference call, Yingdi reveals the plan of using a synchronous API:
- The API is synchronous, ie. will return the requested item (eg. certificate).
- Inside the function call, a default-constructed Face will be used to express the Interest, and then
.processEvents()
will be called on that Face. This ensures no other calls can be executed on the sameio_service
. - The Interest will have a "relative small" InterestLifetime to reduce blocking issue.
There are 3 issues in this plan:
- A default-constructed Face may not be able to connect to a forwarder.
An application may explicitly pass a
Transport
instance to Face constructor in order to talk to a forwarder, in an environment where the default-constructed Face does not work. - Two faces are opened on NFD side, doubling the Face maintenance overhead.
- No matter how short the InterestLifetime is, it affects application performance by blocking a thread.
I do not disagree with a synchronous API as a short term solution.
But the final solution should be a completely asynchronous API from KeyChain to Pib and Tpm (including #2488).
Updated by Junxiao Shi about 9 years ago
Yingdi agrees at 20150817 conference call that the final solution should be asynchronous because it involves network operation.
Updated by Junxiao Shi about 9 years ago
- Blocks Bug #2407: Local certificate is not published added
Updated by Davide Pesavento about 8 years ago
- Subject changed from Make KeyChain to use PIB Service to Make KeyChain use PIB Service
- Target version deleted (
v0.4)
Updated by Alex Afanasyev almost 8 years ago
- Tracker changed from Task to Feature
- Assignee deleted (
Yingdi Yu)
Updated by Junxiao Shi over 7 years ago
- Status changed from New to Rejected
This is no longer relevant because SecPublicInfo
belong to KeyChain v1 which is deprecated.