Alamofire-Response

一.默認(rèn)Response-DefaultDataResponse

  • 返回二進(jìn)制數(shù)據(jù)Data,響應(yīng)示例:
        SessionManager.default.request(urlString).response { (response) in
            print("\(response)")
        }
  • 查看源碼:
    public func response(queue: DispatchQueue? = nil, completionHandler: @escaping (DefaultDataResponse) -> Void) -> Self {
        delegate.queue.addOperation {
            (queue ?? DispatchQueue.main).async {
                var dataResponse = DefaultDataResponse(
                    request: self.request,
                    response: self.response,
                    data: self.delegate.data,
                    error: self.delegate.error,
                    timeline: self.timeline
                )
                dataResponse.add(self.delegate.metrics)
                completionHandler(dataResponse)
            }
        }
        return self
    }
  • 在這里將self.request,self.response,self.delegate.data,self.delegate.error,self.timeline,整合成DefaultDataResponse對(duì)象,同時(shí)將dataResponse交給了DispatchQueue.main主隊(duì)列回調(diào)出去,方便用戶在請(qǐng)求回調(diào)中處理UI事件。
  • 很明顯,DefaultDataResponse傳遞到外面的是原始的二進(jìn)制數(shù)據(jù),
class DataTaskDelegate: TaskDelegate, URLSessionDataDelegate {
    var dataTask: URLSessionDataTask { return task as! URLSessionDataTask }
    override var data: Data? {
        if dataStream != nil {
            return nil
        } else {
            return mutableData
        }
    }
  • 那么這些數(shù)據(jù)什么時(shí)候賦值的?
    func urlSession(_ session: URLSession, dataTask: URLSessionDataTask, didReceive data: Data) {
        if initialResponseTime == nil { initialResponseTime = CFAbsoluteTimeGetCurrent() }
        if let dataTaskDidReceiveData = dataTaskDidReceiveData {
            dataTaskDidReceiveData(session, dataTask, data)
        } else {
            if let dataStream = dataStream {
                dataStream(data)
            } else {
                //處理數(shù)據(jù)
                mutableData.append(data)
            }
            let bytesReceived = Int64(data.count)
            totalBytesReceived += bytesReceived
            let totalBytesExpected = dataTask.response?.expectedContentLength ?? NSURLSessionTransferSizeUnknown
            progress.totalUnitCount = totalBytesExpected
            progress.completedUnitCount = totalBytesReceived
            if let progressHandler = progressHandler {
                progressHandler.queue.async { progressHandler.closure(self.progress) }
            }
        }
    }
  • func urlSession(_ session: URLSession, dataTask: URLSessionDataTask, didReceive data: Data)方法,收到數(shù)據(jù)的時(shí)候,就將mutableData.append(data)追加到了mutableData中,然后通過(guò)response中的completionHandler(dataResponse)回調(diào)給用戶。
  • 至于error的傳遞和賦值,同上查找方法可知,在收到錯(cuò)誤的時(shí)候,賦值self.error
func urlSession(_ session: URLSession, task: URLSessionTask, didCompleteWithError error: Error?) {
        if let taskDidCompleteWithError = taskDidCompleteWithError {
            taskDidCompleteWithError(session, task, error)
        } else {
            if let error = error {
                //賦值error
                if self.error == nil { self.error = error }
                if
                    let downloadDelegate = self as? DownloadTaskDelegate,
                    let resumeData = (error as NSError).userInfo[NSURLSessionDownloadTaskResumeData] as? Data
                {
                    downloadDelegate.resumeData = resumeData
                }
            }
            queue.isSuspended = false
        }
    }

通過(guò)上面的分析,可能會(huì)有疑問(wèn),這么強(qiáng)大的框架,只是原封不動(dòng)的把二進(jìn)制數(shù)據(jù)傳出來(lái),會(huì)不會(huì)有點(diǎn)low? 查看其他的response可知,Alamofire還有針對(duì)響應(yīng)數(shù)據(jù)的序列化操作

二. DataResponse

1. 自定義序列化器

  • 此處自定義了responseSerializer序列化器,返回序列化后的數(shù)據(jù)Result<value>
        SessionManager.default.request(urlString).response(responseSerializer: DataResponseSerializer<String>.init(serializeResponse: { (reques, response, data, error) -> Result<String> in
            print("原始數(shù)據(jù):\(String(describing: response ?? nil))")
            return .success("請(qǐng)求數(shù)據(jù)成功")
        })) { (dataResponse) in
            print("\(dataResponse)")
        }
        SessionManager.default.request(urlString).response { (response) in
            print("\(response)")
        }
  • 源碼分析:
    public func response<T: DataResponseSerializerProtocol>(
        queue: DispatchQueue? = nil,
        responseSerializer: T,
        completionHandler: @escaping (DataResponse<T.SerializedObject>) -> Void)
        -> Self
    {
        delegate.queue.addOperation {
            let result = responseSerializer.serializeResponse(
                self.request,
                self.response,
                self.delegate.data,
                self.delegate.error
            )
            var dataResponse = DataResponse<T.SerializedObject>(
                request: self.request,
                response: self.response,
                data: self.delegate.data,
                result: result,
                timeline: self.timeline
            )
            dataResponse.add(self.delegate.metrics)
            (queue ?? DispatchQueue.main).async { completionHandler(dataResponse) }
        }
        return self
    }
  • 首先序列化數(shù)據(jù),let result = responseSerializer.serializeResponse,返回Result<Value>類(lèi)型,通過(guò)局部變量result保存:
public struct DataResponseSerializer<Value>: DataResponseSerializerProtocol {
    public typealias SerializedObject = Value
    public var serializeResponse: (URLRequest?, HTTPURLResponse?, Data?, Error?) -> Result<Value>
    public init(serializeResponse: @escaping (URLRequest?, HTTPURLResponse?, Data?, Error?) -> Result<Value>) {
        self.serializeResponse = serializeResponse
    }
}
  • 調(diào)用DataResponse整合數(shù)據(jù),返回?cái)?shù)據(jù)多了一個(gè)result,這個(gè)就是我們序列化后的數(shù)據(jù),然后將數(shù)據(jù)回調(diào)到主線程。由于我們自定義了序列化器,所以在外部序列化的時(shí)候,我們可以對(duì)返回的數(shù)據(jù)進(jìn)行預(yù)處理,以滿足我們的需求。

2.自帶responseJSON

        SessionManager.default
            .request(urlString)
            .response { (response) in
                print(response)
            }.responseJSON { (jsonResponse) in
                print(jsonResponse)
        }
  • 源碼分析:
    public func responseJSON(
        queue: DispatchQueue? = nil,
        options: JSONSerialization.ReadingOptions = .allowFragments,
        completionHandler: @escaping (DataResponse<Any>) -> Void)
        -> Self
    {
        return response(
            queue: queue,
            responseSerializer: DataRequest.jsonResponseSerializer(options: options),
            completionHandler: completionHandler
        )
    }
  • responseSerializer傳入DataRequest.jsonResponseSerializer(options: options)序列化參數(shù)
    public static func jsonResponseSerializer(
        options: JSONSerialization.ReadingOptions = .allowFragments)
        -> DataResponseSerializer<Any>
    {
        return DataResponseSerializer { _, response, data, error in
            return Request.serializeResponseJSON(options: options, response: response, data: data, error: error)
        }
    }
  • 繼續(xù)Request.serializeResponseJSON
    public static func serializeResponseJSON(
        options: JSONSerialization.ReadingOptions,
        response: HTTPURLResponse?,
        data: Data?,
        error: Error?)
        -> Result<Any>
    {
        guard error == nil else { return .failure(error!) }

        if let response = response, emptyDataStatusCodes.contains(response.statusCode) { return .success(NSNull()) }

        guard let validData = data, validData.count > 0 else {
            return .failure(AFError.responseSerializationFailed(reason: .inputDataNilOrZeroLength))
        }

        do {
            let json = try JSONSerialization.jsonObject(with: validData, options: options)
            return .success(json)
        } catch {
            return .failure(AFError.responseSerializationFailed(reason: .jsonSerializationFailed(error: error)))
        }
    }
  • 有木有發(fā)現(xiàn),我們自定義的序列化器和系統(tǒng)實(shí)現(xiàn)的serializeResponseJSON序列化如出一轍。本質(zhì)上都是傳入一個(gè)序列化參數(shù),對(duì)數(shù)據(jù)進(jìn)行處理。

三.DefaultDownloadResponseDownloadResponse

  • DefaultDownloadResponse
    public func response(
        queue: DispatchQueue? = nil,
        completionHandler: @escaping (DefaultDownloadResponse) -> Void)
        -> Self
    {
        delegate.queue.addOperation {
            (queue ?? DispatchQueue.main).async {
                var downloadResponse = DefaultDownloadResponse(
                    request: self.request,
                    response: self.response,
                    temporaryURL: self.downloadDelegate.temporaryURL,
                    destinationURL: self.downloadDelegate.destinationURL,
                    resumeData: self.downloadDelegate.resumeData,
                    error: self.downloadDelegate.error,
                    timeline: self.timeline
                )
                downloadResponse.add(self.delegate.metrics)
                completionHandler(downloadResponse)
            }
        }
        return self
    }
  • DownloadResponse
public func response<T: DownloadResponseSerializerProtocol>(
        queue: DispatchQueue? = nil,
        responseSerializer: T,
        completionHandler: @escaping (DownloadResponse<T.SerializedObject>) -> Void)
        -> Self
    {
        delegate.queue.addOperation {
            let result = responseSerializer.serializeResponse(
                self.request,
                self.response,
                self.downloadDelegate.fileURL,
                self.downloadDelegate.error
            )
            var downloadResponse = DownloadResponse<T.SerializedObject>(
                request: self.request,
                response: self.response,
                temporaryURL: self.downloadDelegate.temporaryURL,
                destinationURL: self.downloadDelegate.destinationURL,
                resumeData: self.downloadDelegate.resumeData,
                result: result,
                timeline: self.timeline
            )
            downloadResponse.add(self.delegate.metrics)
            (queue ?? DispatchQueue.main).async { completionHandler(downloadResponse) }
        }
        return self
    }
  • 序列化
public struct DownloadResponseSerializer<Value>: DownloadResponseSerializerProtocol {
    public typealias SerializedObject = Value
    public var serializeResponse: (URLRequest?, HTTPURLResponse?, URL?, Error?) -> Result<Value>
    public init(serializeResponse: @escaping (URLRequest?, HTTPURLResponse?, URL?, Error?) -> Result<Value>) {
        self.serializeResponse = serializeResponse
    }
}
  • DefaultDownloadResponseDownloadResponse,對(duì)于序列化的處理與DefaultDataResponseDataResponse大同小異;
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請(qǐng)聯(lián)系作者
【社區(qū)內(nèi)容提示】社區(qū)部分內(nèi)容疑似由AI輔助生成,瀏覽時(shí)請(qǐng)結(jié)合常識(shí)與多方信息審慎甄別。
平臺(tái)聲明:文章內(nèi)容(如有圖片或視頻亦包括在內(nèi))由作者上傳并發(fā)布,文章內(nèi)容僅代表作者本人觀點(diǎn),簡(jiǎn)書(shū)系信息發(fā)布平臺(tái),僅提供信息存儲(chǔ)服務(wù)。

相關(guān)閱讀更多精彩內(nèi)容

  • 在上兩篇中研究了下Alamofire的請(qǐng)求發(fā)起過(guò)程以及在請(qǐng)求發(fā)起過(guò)程中一些有用的功能,本篇來(lái)看看數(shù)據(jù)接受的環(huán)節(jié) r...
    好有魔力閱讀 746評(píng)論 0 4
  • 上幾篇介紹了Alamofire的SessionManager,SessionDelegate,Request等等。...
    king_jensen閱讀 730評(píng)論 0 4
  • response為數(shù)據(jù)請(qǐng)求響應(yīng)結(jié)果,封裝了URLRequest、時(shí)間軸、請(qǐng)求錯(cuò)誤信息,請(qǐng)求成功的數(shù)據(jù)等信息,方便開(kāi)...
    yahibo閱讀 697評(píng)論 0 4
  • ??????Alamofire專(zhuān)題目錄,歡迎及時(shí)反饋交流 ??????Alamofire (1)—— URLSession必備...
    Cooci_和諧學(xué)習(xí)_不急不躁閱讀 1,483評(píng)論 4 8
  • 一、Response 1、Response: 信息保存者,面向?qū)ο?點(diǎn)擊response 點(diǎn)擊self.deleg...
    Code_人生閱讀 291評(píng)論 1 3

友情鏈接更多精彩內(nèi)容