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` structure, ranging from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `Crc32cChecksumValue` structure is related to pre-computing CRC32C checksums, which enhances data integrity verification when an application can obtain the checksum out-of-band."],["Providing a pre-computed CRC32C checksum can improve end-to-end data integrity, especially when data is obtained from other cloud services or when the GCS object metadata has already been queried."],["The content includes information about a static `name()` function, as well as a default constructor, within the `Crc32cChecksumValue` struct."]]],[]]
