What's the best practice for retrying a request without using the durable function? If the client is closed and then reopened I don't want it to send these requests at a later time.
I would like to retry a number of times and then handle the error if after n tries the request still fail and the client needs to handle that. Do I need to write a custom retry handler?
If you are using Unity, then the durable requests will take care of this for you. They will only be sent when GameSparks gets a connection to the server, not when the app is unpaused or suspended. So durable request wont try to send and fail because the app is reopened.
Does that make sense? Let me know if i am misunderstanding
If you are using Unity, then the durable requests will take care of this for you. They will only be sent when GameSparks gets a connection to the server, not when the app is unpaused or suspended. So durable request wont try to send and fail because the app is reopened.
Does that make sense? Let me know if i am misunderstanding
Thanks, Sean
K
Kevin Baxtrom
said
about 4 years ago
Just to clarify. Let's say we have not lost connection from the gamesparks server, but the request has failed. Maybe a slow connection or the request just timed out. I should still use the durable request?
The documentation seems to suggest it will retry once the user is re-authenticated, but not necessarily if the request timed out for other reasons.
Customer Support
said
over 3 years ago
yes, in this case a durable request will still work once you establish a connection again.
Kevin Baxtrom
What's the best practice for retrying a request without using the durable function? If the client is closed and then reopened I don't want it to send these requests at a later time.
I would like to retry a number of times and then handle the error if after n tries the request still fail and the client needs to handle that. Do I need to write a custom retry handler?
https://support.gamesparks.net/support/discussions/topics/1000044588
Hey Kevin,
If you are using Unity, then the durable requests will take care of this for you.
They will only be sent when GameSparks gets a connection to the server, not when the app is unpaused or suspended.
So durable request wont try to send and fail because the app is reopened.
Does that make sense?
Let me know if i am misunderstanding
Thanks,
Sean
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstCustomer Support
Hey Kevin,
If you are using Unity, then the durable requests will take care of this for you.
They will only be sent when GameSparks gets a connection to the server, not when the app is unpaused or suspended.
So durable request wont try to send and fail because the app is reopened.
Does that make sense?
Let me know if i am misunderstanding
Thanks,
Sean
Kevin Baxtrom
Just to clarify. Let's say we have not lost connection from the gamesparks server, but the request has failed. Maybe a slow connection or the request just timed out. I should still use the durable request?
The documentation seems to suggest it will retry once the user is re-authenticated, but not necessarily if the request timed out for other reasons.
Customer Support
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2486 topics