Fix : Slow server response. #616 #617
Open
+46
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added a global OkHttpClient with long timeouts and initialized AndroidNetworking with it.
I replaced per-request new OkHttpClient() usages with the shared client to avoid overriding the longer timeouts.
I aligned the Rx sample apps to initialize with the same client.
Updated app/src/main/java/com/networking/MyApplication.java to build an OkHttpClient with 120s connect/read/write timeouts and pass it to AndroidNetworking.initialize(...). Exposed getOkHttpClient() to reuse.
Updated per-request overrides in app:
Updated Rx sample apps to use the same approach:
Contribution by Gittensor, learn more at https://gittensor.io/
This ensures slow server responses (50–60s) won’t trigger premature onError due to client-side timeouts.