【发布时间】:2021-03-18 04:02:29
【问题描述】:
我正在编写一个自定义图像获取器来获取我的收藏视图所需的图像。下面是我的图像获取器逻辑
class ImageFetcher {
/// Thread safe cache that stores `UIImage`s against corresponding URL's
private var cache = Synchronised([URL: UIImage]())
/// Inflight Requests holder which we can use to cancel the requests if needed
/// Thread safe
private var inFlightRequests = Synchronised([UUID: URLSessionDataTask]())
func fetchImage(using url: URL, completion: @escaping (Result<UIImage, Error>) -> Void) -> UUID? {
/// If the image is present in cache return it
if let image = cache.value[url] {
completion(.success(image))
}
let uuid = UUID()
let dataTask = URLSession.shared.dataTask(with: url) { [weak self] data, response, error in
guard let self = self else { return }
defer {
self.inFlightRequests.value.removeValue(forKey:uuid )
}
if let data = data, let image = UIImage(data: data) {
self.cache.value[url] = image
DispatchQueue.main.async {
completion(.success(image))
}
return
}
guard let error = error else {
// no error , no data
// trigger some special error
return
}
// Task cancelled do not send error code
guard (error as NSError).code == NSURLErrorCancelled else {
completion(.failure(error))
return
}
}
dataTask.resume()
self.inFlightRequests.value[uuid] = dataTask
return uuid
}
func cancelLoad(_ uuid: UUID) {
self.inFlightRequests.value[uuid]?.cancel()
self.inFlightRequests.value.removeValue(forKey: uuid)
}
}
这是一个提供访问缓存所需的线程安全性的代码块
/// Use to make a struct thread safe
public class Synchronised<T> {
private var _value: T
private let queue = DispatchQueue(label: "com.sync", qos: .userInitiated, attributes: .concurrent)
public init(_ value: T) {
_value = value
}
public var value: T {
get {
return queue.sync { _value }
}
set { queue.async(flags: .barrier) { self._value = newValue }}
}
}
我没有看到所需的滚动性能,我预计这是因为当我尝试访问缓存时我的主线程被阻塞 (queue.sync { _value })。我正在从 collectionView 的 cellForRowAt 方法调用 fetchImage 方法,但我似乎找不到将其从主线程分派出去的方法,因为我需要请求的 UUID,因此我可以取消请求如果需要的话。关于如何将其从主线程中移除的任何建议,或者是否有任何建议以更好的方式构建它?
【问题讨论】:
标签: ios multithreading grand-central-dispatch data-synchronization barrier