aboutsummaryrefslogtreecommitdiff
path: root/backends/cloud/basestorage.h
diff options
context:
space:
mode:
authorAlexander Tkachev2019-07-16 14:09:38 +0700
committerMatan Bareket2019-07-30 14:51:41 -0400
commite8669f693c6adbb33f515d9a4ce9d1079756e2e8 (patch)
treea11d17b6706c9c21ea78ae92ff113f860f7d97e9 /backends/cloud/basestorage.h
parent60504dce7539863a207610fd636236c7035ade3e (diff)
downloadscummvm-rg350-e8669f693c6adbb33f515d9a4ce9d1079756e2e8.tar.gz
scummvm-rg350-e8669f693c6adbb33f515d9a4ce9d1079756e2e8.tar.bz2
scummvm-rg350-e8669f693c6adbb33f515d9a4ce9d1079756e2e8.zip
CLOUD: Update BaseStorage to expect no refresh_token
While refreshing access_token, some cloud providers also pass a new refresh_token. Google Drive does not, and accepts the same refresh_token next time. These changes allow this to happen.
Diffstat (limited to 'backends/cloud/basestorage.h')
-rw-r--r--backends/cloud/basestorage.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/backends/cloud/basestorage.h b/backends/cloud/basestorage.h
index 4b3b497d0d..243e7f4bcc 100644
--- a/backends/cloud/basestorage.h
+++ b/backends/cloud/basestorage.h
@@ -69,6 +69,11 @@ protected:
*/
virtual bool needsRefreshToken() = 0;
+ /**
+ * Return whether to expect new refresh_token on refresh.
+ */
+ virtual bool canReuseRefreshToken() = 0;
+
private:
void tokenRefreshed(BoolCallback callback, Networking::JsonResponse response);