Is this method side-effect-free (or safe in HTTP parlance), or idempotent,
or neither? HTTP based RPC implementation may choose GET verb for safe
methods, and PUT verb for idempotent methods instead of the default POST.
[[["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-08-07 UTC."],[[["This document describes the `MethodOptions.Types.IdempotencyLevel` enum within the `Google.Protobuf.Reflection` namespace."],["This enum is used to define the idempotency level of a method, including whether it has no side effects, is idempotent, or its idempotency is unknown."],["It provides three possible values: `IdempotencyUnknown`, `Idempotent` (which may have side effects), and `NoSideEffects` (which implies idempotent)."],["HTTP-based RPC implementations may use GET or PUT verbs based on the idempotency level instead of the default POST."],["This information is available in multiple versions of the `Google.Protobuf` library, with links provided to versions 3.27.1, 3.23.0, and 3.15.8."]]],[]]
