Looping storage service writes and deletes ?

[Tom Zeller]

Mostly Scott,

When writing or deleting consent storage records, should I attempt the
write or delete once or loop several times like
StorageBackedIdpSession.saveAuthenticationResultToStorage() ?

Not a big deal, but, when maintaining the index record whose value is
the storage keys for the storage context, it's possible for the value
to be empty, for example, after all records have expired. So, I would
need to track whether the storage record exists and is empty or
whether it doesn't exist to know whether to call
StorageService.create() or update(). I guess calling create() and then
update() works, but that seems possibly noisy if the storage service
is server-side.

Thanks.