Lines Matching full:strategy
140 …ch complicates state management in the core. Given the likely complexity, we exclude this strategy.
156 * [Always follow the state of the secure element](#exploring-the-follow-the-secure-element-strategy…
157 …tion processing: [always destroy the key](#exploring-the-always-destroy-strategy), i.e. abort all …
158 …rrupted. These do not seem like decisive advantages, so we will not consider this strategy further.
159 … of the secure element for key destruction. I can't think of a good reason to choose this strategy.
161 …o that it can find a free slot when creating a key. But with a recovery strategy that doesn't invo…
163 #### Exploring the follow-the-secure-element strategy
192 #### Exploring the always-destroy strategy
217 #### Always-destroy strategy with a simpler transaction file
219 We can modify the [always-destroy strategy](#exploring-the-always-destroy-strategy) to make the tra…
243 Compared with the basic always-destroy strategy:
254 This gives an advantage to the “always destroy” strategy. Under this strategy, if the key might be …
260 #### Naive test strategy for non-atomic processes
264 Our general strategy to test them is as follows: every time there is a modification of persistent s…
384 …very), we pick the [always-destroy recovery strategy with a simple transaction file](#always-destr…