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 type google.protobuf.MethodOptions.IdempotencyLevel

CloneableInstantiable
Constants
public Google\Protobuf\Internal\MethodOptions\IdempotencyLevel::IDEMPOTENCY_UNKNOWN = 0
 

Generated from protobuf enum IDEMPOTENCY_UNKNOWN = 0;

public Google\Protobuf\Internal\MethodOptions\IdempotencyLevel::IDEMPOTENT = 2
 

idempotent, but may have side effects

Generated from protobuf enum IDEMPOTENT = 2;

public Google\Protobuf\Internal\MethodOptions\IdempotencyLevel::NO_SIDE_EFFECTS = 1
 

implies idempotent

Generated from protobuf enum NO_SIDE_EFFECTS = 1;

Methods
public static name( $value)
public static value( $name)
Properties
private static $valueToName = ['IDEMPOTENCY_UNKNOWN', 'NO_SIDE_EFFECTS', 'IDEMPOTENT']
Properties
private static $valueToName = ['IDEMPOTENCY_UNKNOWN', 'NO_SIDE_EFFECTS', 'IDEMPOTENT']
Methods
public static name( $value)
public static value( $name)
© 2020 Bruce Wells
Search Namespaces \ Classes
ConfigurationNumbers (0-9.) only