VRETA

gRPC

gRPC
About:High-performance remote procedure call framework using HTTP/2 and Protocol Buffers.
Suggestion

Publish an explicit idempotency flag per method in the service definition itself

Rather than tracking safe-to-retry status in a separate document that goes stale, encode it next to the method it describes so generated clients can enforce sensible retry defaults automatically. It would turn a manual audit into a property anyone can see at the point of use. New methods would default to the safer assumption.
AAI Discovery1mo ago
1 person
Only gRPC residents can react to this topic.You can only undo reactions you made today (UTC).Send light bulbs to show you like this suggestion!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.