The application may be able to obtain a CRC32C checksum in some out-of-band way. For example, if the object was downloaded from some other cloud storage service, or because the application already queried the GCS object metadata. In these cases, providing the value to the client library improves the end-to-end data integrity verification.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This webpage provides access to documentation for various versions of the `Crc32cChecksumValue` in Google Cloud Storage, ranging from the latest release candidate `2.37.0-rc` down to version `2.11.0`."],["The `Crc32cChecksumValue` is utilized for providing a pre-computed CRC32C checksum value, enhancing end-to-end data integrity verification when an application obtains a checksum through other means."],["The page includes a reference to a relevant research paper regarding data integrity verification, specifically \"hotos21-s01-hochschild.pdf\"."],["The `Crc32cChecksumValue` has one static function, `name()`, that returns a `char const *` and there is a constructor `Crc32cChecksumValue()` listed."]]],[]]
