Verified SetAll and GetAll?

[mlieberman85]

I am not sure if I'm missing something or if creating groups of Verified commands isn't currently supported. If it isn't supported I think it would be a good feature.

It would allow for atomic operations that could be verified. My use case is I have a set of set commands that constitute a single atomic operation and want to validate that all of them weren't tampered with and also should roll back in the event of a failure like a normal SetAll.

[jeroiraz]

Hi @mlieberman85, thanks for reaching out.

Set or SetAll are the same operation, only the method signature in the SDK differs, the first one receiving the key and value as parameters, while the second one receiving a list of pairs. In both cases the server will create a single transaction including the single or multiple entries provided, so the change will be atomic.

Get and GetAll are similar, but for resolving GetAll the server will execute multiple Get operations. The benefit of using GetAll is to reduce the number of requests made from the client to the server.

Regarding verification, having single entry verification or multi-entry verification won't increase nor decrease security but it may reduce the number of requests the client application needs to made to the server.

I think having VerifiedSetAll is a good functionality to have, because given all the key-value pairs belong to the same transaction, it would be much faster to validate than verifying entry by entry.