Enable HTTP connection reuse for okhttp #1907
Merged
+28
−16
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.
Purpose
Enable HTTP connection reuse and keep-alive for WebDAV connections to improve performance and reduce connection overhead.
This only applies to okhttp connections and not to Ktor, which manages engine client reuse itself (can be verified / tested at a later time).
It applies to all HTTP operations, so both sync and WebDAV.
Short description
OkHttpClientinstance for connection poolingsharedOkHttpClient.newBuilder()for new client instances instead of creating new clients from scratchbuildTimeouts()methodThis change allows OkHttp to reuse connections and share thread pools across different HTTP clients, which is especially beneficial for WebDAV operations that often involve multiple sequential requests to the same server.
Checklist