Skip to content

Commit 5e07588

Browse files
committed
firewalldb: address last few comments from #763
1 parent 33d717a commit 5e07588

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

firewalldb/kvstores.go

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The KVStores are stored in the following structure in the KV db. Note that
1212
the `perm` and `temp` buckets are identical in structure. The only difference
1313
is that the `temp` bucket is cleared on restart of the db. The reason persisting
1414
the temporary store changes instead of just keeping an in-memory store is that
15-
we can then guarantee idempotency if changes are made to both the permanent and
15+
we can then guarantee atomicity if changes are made to both the permanent and
1616
temporary stores.
1717
1818
rules -> perm -> rule-name -> global -> {k:v}
@@ -86,14 +86,14 @@ type KVStoreTx interface {
8686
// GlobalTemp is similar to the Global store except that its contents
8787
// is cleared upon restart of the database. The reason persisting the
8888
// temporary store changes instead of just keeping an in-memory store is
89-
// that we can then guarantee idempotency if changes are made to both
89+
// that we can then guarantee atomicity if changes are made to both
9090
// the permanent and temporary stores.
9191
GlobalTemp() KVStore
9292

9393
// LocalTemp is similar to the Local store except that its contents is
9494
// cleared upon restart of the database. The reason persisting the
9595
// temporary store changes instead of just keeping an in-memory store is
96-
// that we can then guarantee idempotency if changes are made to both
96+
// that we can then guarantee atomicity if changes are made to both
9797
// the permanent and temporary stores.
9898
LocalTemp() KVStore
9999
}

0 commit comments

Comments
 (0)