You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idempotent requests are now rejected with a 159 code error,
Feature / Enhancement Description
Instead of rejecting with an error, maybe there is a way to cache the response and respond with it on the next request?.
Example Use Case
A client SDK creates a Test ParseObject but doesn't recieve the response because of a network issue, the SDK tries to create the object again with the same X-Parse-Request-Id header, the server replies with the same object creation response instead of creating a new one.
Alternatives / Workarounds
N/A
3rd Party References
N/A
The text was updated successfully, but these errors were encountered:
I have an android app where I am creating a Post ParseObject, but when connection issues arise creating a post can sometimes return with the error code 159. And then the app will have to figure out how to query this newly crerated post.
I think caching the response server side on the same _Idempotency collection for the same amount of time the ttl is set in the idempotencyOptions configuration... might solve this issue.
Got it. This has been discussed in the design of this feature, see #6748 (comment) and #6748 (comment). Maybe @mrmarcsmith would be interested to join this discussion here to find a concept for returning cached responses.
New Feature / Enhancement Checklist
Current Limitation
Idempotent requests are now rejected with a
159
code error,Feature / Enhancement Description
Instead of rejecting with an error, maybe there is a way to cache the response and respond with it on the next request?.
Example Use Case
A client SDK creates a
Test
ParseObject but doesn't recieve the response because of a network issue, the SDK tries to create the object again with the sameX-Parse-Request-Id
header, the server replies with the same object creation response instead of creating a new one.Alternatives / Workarounds
N/A
3rd Party References
N/A
The text was updated successfully, but these errors were encountered: