Use an URLSessionConfiguration that can be configured by app #36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make URLSessionConfiguration configurable by the client
juanarzola
changed the title
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Apps may need custom URLSessionConfiguration in order to function properly. For example, if it uses a custom NSURLProtocol to load image, it needs to set
protocolClassesor content loaded by those custom protocols won't load.CachedAsyncImagestarts its sessions usingURLSessionConfiguration.default, but because it always returns a copy, that can't be used by the app to configure the default configuration with its own unique requirements. In order to support custom configuration, haveCachedAsyncImageuse an internal copy of the default config that is exposed to the app viaURLSessionConfiguration.cachedAsyncImagethat can be modified or set.