3 ms·
Seems like a tail wag. The header is in common use in APIs in the wild, so IETF wants to formalize it. Not unreasonable, but doesn't seem to add much value eit
by quesera 5y ago
Seems like a tail wag. The header is in common use in APIs in the wild, so IETF wants to formalize it.
Not unreasonable, but doesn't seem to add much value either.
With standardization, load balancers or reverse proxies could add a limited idempotency guarantee to reduce the load/implementation cost on the application layer. I don't think anyone is asking for this though, nor do I think they should be...but maybe I'm wrong about that. "Free (quasi) idempotency for small environments" could be a feature.