Not a problem. They are deferred. as usual. The current protocol chain soon pauses as most protocols end up waiting for external queuing service, pit or ledger. Each protocol stack contains a return which encrypts the pipeline and puts it in kernel stack until all the asynchronous services complete. Then we get a restore code.
The whole trick is to find some kernel controlled, non memory mapped register to hold a secret key. Then make sure the kernel path through the stack is closed to stable, finite, testable states.
Some of this is overkill, and the insurance companies will lower these standards if the other asynchronous IO is controlled. Pipeline usage ends up priced, and abuse can lower profit margins for insurance companies. insurance companies will generally want their own pipeline watch dog running a separate process.
No comments:
Post a Comment