verifyObject was initially introduced to help the client manage the scenario where only a data object is stored and subsequently determined to be no longer needed. After further discussion with @taojing2002, we have determined that this utility method should be included.
Since we have the signature for storeObject(InputStream), the client should have a way to reverse this process. Not providing this functionality and leaving it to the client could lead to unnecessary complications, as they might need to directly calculate the address of the data object (and be forced to bypass the HashStore Public API).
We will rename verifyObject to deleteInvalidObject for clarity purposes.
verifyObject
was initially introduced to help the client manage the scenario where only a data object is stored and subsequently determined to be no longer needed. After further discussion with @taojing2002, we have determined that this utility method should be included.Since we have the signature for
storeObject(InputStream)
, the client should have a way to reverse this process. Not providing this functionality and leaving it to the client could lead to unnecessary complications, as they might need to directly calculate the address of the data object (and be forced to bypass theHashStore
Public API).We will rename
verifyObject
todeleteInvalidObject
for clarity purposes.