We should have a long time before the on-disk representation becomes a problem, so I'd defer messing with that until the Swift backend has been well bedded or abandoned.
We should have a long time before the on-disk representation becomes a problem, so I'd defer messing with that until the Swift backend has been well bedded or abandoned.