Last post Mar 03, 2015 08:38 PM by trsuman
Mar 02, 2015 04:46 PM|trsuman|LINK
I have seen http headers like x-ms-tracking-id in rest services which would be a unique identifier when sending a (post/put/patch) request to a REST API. The server would detect the tracking id header and in case if it was a duplicate, the server would reject
the request. This provides for idempotency for clients and help in timeout scenarios.
Question is: What are some good patterns to implement above in asp net Web API? Which storage to use to make this happen without significant perf impact?
The tracking-id obviously has to be stored and every request(post/put/patch) incurs the cost of lookup which has a perf impact.
This is more of a design question so please share thoughts on pros/cons of doing this.
Mar 03, 2015 02:01 AM|LemonStreet|LINK
You can take a look at the information within the link below:
Mar 03, 2015 08:38 PM|trsuman|LINK
How is this relevant to what I have asked?