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-04-01 UTC."],[[["This webpage provides access to the `Crc32cChecksumValue` documentation for various versions of the C++ client library, ranging from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `Crc32cChecksumValue` can be used by applications to improve end-to-end data integrity verification when a pre-computed CRC32C checksum is available through some means outside the library."],["The page references a paper on data integrity from the SIGOPS HotOS 2021 conference, showing where data integrity is discussed."],["The documentation includes details about the `Crc32cChecksumValue` constructor and the static `name()` function, which returns a `char const *`."]]],[]]
