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-02 UTC."],[[["The page provides access to the `Crc32cChecksumValue` structure documentation across multiple versions, from 2.11.0 up to the latest release candidate 2.37.0-rc."],["The latest version available is 2.37.0-rc, while 2.19.0 is the lowest version listed in the provided information, and 2.36.0 being the current release."],["The `Crc32cChecksumValue` structure is related to pre-computed CRC32C checksum values, which can be supplied to the client library to improve data integrity verification."],["The page provides links to documentation for the `Crc32cChecksumValue` structure's constructors and functions, specifically the static `name()` function, for each version."],["The `name()` function, with a return type of `char const *` does not have any listed description."]]],[]]
