Thomas H. Austin
Thomas H. Austin
Correct me if I am wrong, but don't the write markers connect to the metadata? Assuming the markers are signed by the client, that should prevent the blobber from presenting...
It sounds like we might be able to resolve this issue by adding the fileMetaData (or a hash of it) into the marker. Any issues with that approach?
I agree that concurrent updates from different devices would be a concern. Any worry about the size of the random FileID? If so, another option might be to assign a...
So the idea is to use the writemarker locking mechanism to make sure that we don't have conflicts on the fileID numbering? If so, I'm good with that.