Launch the Interceptor chain on the main thread by default. #513
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.
This PR changes the default behaviour of the interceptor chain to be launched on the main thread by default. Why do this:
Interceptors
to be execute on the main thread synchronously if preferred.Interceptors
can also control which requests check the memory cache on the main thread by usingwithContext
to change the current dispatcher when callingInterceptor.Chain.proceed
.0.12.0
. This realigns with that behaviour, but allows consumers to move the check off the main thread if they want maximum performance.This PR adds two new flags to
ImageLoader.Builder
:launchInterceptorChainOnMainThread
: Enables/disables launching the interceptor chain on the main thread.addLastModifiedToFileCacheKey
: If the memory cache check occurs on the main thread, callingFile.lastModified
can cause a strict mode violation. This flag disables callingFile.lastModified
. See Add option to disable adding File.lastModified to the cache key. #415 for context.Fixes: #280