public enum DescriptorProtos.MethodOptions.IdempotencyLevel extends Enum<DescriptorProtos.MethodOptions.IdempotencyLevel> implements ProtocolMessageEnum
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.
Protobuf enum google.protobuf.MethodOptions.IdempotencyLevel
Implements
ProtocolMessageEnumStatic Fields |
|
---|---|
Name | Description |
IDEMPOTENCY_UNKNOWN |
|
IDEMPOTENCY_UNKNOWN_VALUE |
|
IDEMPOTENT |
idempotent, but may have side effects |
IDEMPOTENT_VALUE |
idempotent, but may have side effects |
NO_SIDE_EFFECTS |
implies idempotent |
NO_SIDE_EFFECTS_VALUE |
implies idempotent |
Static Methods |
|
---|---|
Name | Description |
forNumber(int value) |
|
getDescriptor() |
|
internalGetValueMap() |
|
valueOf(Descriptors.EnumValueDescriptor desc) |
|
valueOf(int value) |
Deprecated. Use #forNumber(int) instead. |
valueOf(String name) |
|
values() |
Methods |
|
---|---|
Name | Description |
getDescriptorForType() |
Return the enum type's descriptor, which contains information about each defined value, etc. |
getNumber() |
Return the value's numeric value as defined in the .proto file. |
getValueDescriptor() |
Return the value's descriptor, which contains information such as value name, number, and type. |