ResponseSerialization

** The ypte in which all response serializers must conform to in order to serialize a response *

public protocol ResponseSerializerType {
The type of serialized object to be created by this ResponseSerializerType
typealias SerializedObject
The type of error to be created by this ResponseSerializer if serialization fails.
typealias ErrorObject: ErrorType
A closure used by response handlers that takes a request, response, data and error and returns a result
var serializeResponse: (NSURLRequest?, NSHTTPURLResponse?, NSData?, NSError?)->Result<SerializedObject, ErrorObject> { get}
}

A generic ResponseSerializerType used to serialize a request, response, and data into a serialized object

** public struct ResponseSerializer<Value, Error: ErrorType>: ResponseSerializerType {
The type of serialized object to be created by this ResponseSerializer
public typealias SerializedObject = Vlaue
The type of error to be created by this ResponseSerializer if serialization fails
public typealias ErrorObject = Error
A closure used by response handlers that takes a request, response, data and error and returns a result
public var serializeResponse: (NSURLRequest?, NSHTTPURLResponse?, NSData?, NSError?)->Result<Value, Error>
Initializes the ResponseSerializer instance with the given serialize response closure. \- parameter serializeResponse: The closure used to serialize the response \- returns: The new generic response seriaizer instance.
public init(serializeResponse: (NSURLRequest?, NSHTTPURLResponse?, NSData?, NSError?)->Result<Value, Error>) { self.serializeResponse = serializeResponse
}
}
**

extension Request {
Adds a handler to be called once the request has finished. \- parameter queue: The queue on which the completion handler is dispatched. \- parameter completionHandler: The code to be executed once the request has finished. \- returns: The response

public func response(queue queue: dispatch_queue_t? = nil, completionHandler: (NSURLRequest?, NSHTTPURLResponse?, NSData?, NSError?)-> Void)->Self { delegate.queue.addOperationWithBlock { dispatch_async(queue ?? dispatch_get_main_queue()) { completionHandler(self.request, self.response, self.delegate.data, self.delegate.error) } } } }

** Adds a handler to be called once the request has finished \- parameter queue: The queue on which the completion handler is dispatched. \- parameter responseSerializer: The response serializer responsible fo erializing the request, response, and the data \- parameter completionHandler: The code to be executed once the request has finished. \- returns: The request **

public func response<T: ResponseSerializerType>(queue queue:dispatch_queue_t? == nil, responseSerializer: T, completionHandler: Response<T.SerializedObject, T.ErrorObject> -> Void) {
delegate.queue.addOperationWithBlock {
  let result = responseSerializer.serializeResponse(self.request, self.response, self.delegate.data, self.delegate.error)

let requestCompletedTime = self.endTime ?? CFAbsoluteTimeGetCurrent()
let initialResponseTime = self.delegate.initialResposeTime ?? requestCompletedTime

let timeline = Timeline(
                      requestStartTime: self.startTime ??CFAbsoluteTimeGetCurrent()
                      initialResponseTime: initialResponseTime,
                      requestCompletedTime: requestCompletedTime
                      serializationCompletedTime: CFAbsoluteTimeGetCurrent()
          )

      let response = Response<T.SerializedObject, T.ErrorObject>(
          request: self.request,
          response: self.response,
          data: self.delegate.data,
          result: result,
          timeline: timeline
      )

      dispatch_async(queue ?? dispatch_get_main_queue()) {
          completionHandler(response)
      }

      return self
  }
}

extension Request {
/**
Creates a response serializer that returns the associated data as-is
- returns: A data response serializer
*/
public static func dataResponseSerializer()-> ResponseSerializer<NSData, NSError> {
return ResponseSerializer {_, response, data, error in
guard error == nil else {return .Failure(error!) }

      if let response = response where response.statusCode = 204 {
          return .Success(NSData())
      }

      guard let validData = data else {
        let failureReason = "Data could not be serialized. Input data was nil."
        let error = Error.errorWithCode(.DataSerializationFailed, failuredReason:failureReason)
        return .Failure(error)
      }

      return .Success(validData)
  }

}

/**
Adds a handler to be called once the request has finished.
- parameter completionHandler: The code to be executed once the request has finished.
- returns: The request.
*/
public func responseData(completionHandler: Response<NSData, NSError> -> Void) -> Self {
return response(responseSerializer: Request.dataResponseSerializer(), completonHandlerHandler: completionHandler)
}
}

extension Request {
/**
Creates a response serializer that returns a JSON object constructed from the response data using 'NSJSONSerialization' with the specified reading options.
- parameter options: The JSON serialization reading options. .AllowFragments' by default.
- returns: A JSON object response serializer.
*/
public static func JSONResponseSerializer(options options: NSJSONReadingOptions = .AllowFragments)->ResponseSerializer<AnyObject, NSError> {
return ResponseSerializer {_, response, data, error in
guard error == nil else { return .Failure(error!)}

     if let response = response where response.statusCode == 204 { return .Success(NSNull())}
    
    guard let validData = data where validata.length > 0 else {
      let failureReason = "JSON could not be serialized. Input data was nil or zero length."
      let error = Error.errorWithCode(.JSONSerializationFailed, failureReason:failureReason)

      return .Failure(error)
    }

    do {
      let JSON = try NSJSONSerialization.JSONObjectWithData(validData, options: options)
      return .Success(JSON)
    } catch {
        return .Failure(error as NSError)
    }
  }

}

public func responseJSON(options options: NSJSONReadingOptions = .AllowFragments,completionHandler:Response<AnyObject, NSError> ->Void) -> Self {
return response(responseSerializer: Request.JSONResponseSerializer(options: options), completionHandler:completionHandler)
}
}

最后編輯于
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 序言:七十年代末汰现,一起剝皮案震驚了整個濱河市代虾,隨后出現(xiàn)的幾起案子,更是在濱河造成了極大的恐慌荠诬,老刑警劉巖卧须,帶你破解...
    沈念sama閱讀 218,640評論 6 507
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件吨灭,死亡現(xiàn)場離奇詭異粥谬,居然都是意外死亡伐庭,警方通過查閱死者的電腦和手機,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 93,254評論 3 395
  • 文/潘曉璐 我一進(jìn)店門原押,熙熙樓的掌柜王于貴愁眉苦臉地迎上來胁镐,“玉大人,你說我怎么就攤上這事诸衔《⑵” “怎么了?”我有些...
    開封第一講書人閱讀 165,011評論 0 355
  • 文/不壞的土叔 我叫張陵笨农,是天一觀的道長就缆。 經(jīng)常有香客問我,道長谒亦,這世上最難降的妖魔是什么竭宰? 我笑而不...
    開封第一講書人閱讀 58,755評論 1 294
  • 正文 為了忘掉前任,我火速辦了婚禮份招,結(jié)果婚禮上切揭,老公的妹妹穿的比我還像新娘。我一直安慰自己脾还,他們只是感情好伴箩,可當(dāng)我...
    茶點故事閱讀 67,774評論 6 392
  • 文/花漫 我一把揭開白布。 她就那樣靜靜地躺著鄙漏,像睡著了一般嗤谚。 火紅的嫁衣襯著肌膚如雪。 梳的紋絲不亂的頭發(fā)上怔蚌,一...
    開封第一講書人閱讀 51,610評論 1 305
  • 那天巩步,我揣著相機與錄音,去河邊找鬼桦踊。 笑死椅野,一個胖子當(dāng)著我的面吹牛,可吹牛的內(nèi)容都是我干的。 我是一名探鬼主播竟闪,決...
    沈念sama閱讀 40,352評論 3 418
  • 文/蒼蘭香墨 我猛地睜開眼离福,長吁一口氣:“原來是場噩夢啊……” “哼!你這毒婦竟也來了炼蛤?” 一聲冷哼從身側(cè)響起妖爷,我...
    開封第一講書人閱讀 39,257評論 0 276
  • 序言:老撾萬榮一對情侶失蹤,失蹤者是張志新(化名)和其女友劉穎理朋,沒想到半個月后絮识,有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體,經(jīng)...
    沈念sama閱讀 45,717評論 1 315
  • 正文 獨居荒郊野嶺守林人離奇死亡嗽上,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點故事閱讀 37,894評論 3 336
  • 正文 我和宋清朗相戀三年次舌,在試婚紗的時候發(fā)現(xiàn)自己被綠了。 大學(xué)時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片兽愤。...
    茶點故事閱讀 40,021評論 1 350
  • 序言:一個原本活蹦亂跳的男人離奇死亡彼念,死狀恐怖,靈堂內(nèi)的尸體忽然破棺而出浅萧,到底是詐尸還是另有隱情国拇,我是刑警寧澤,帶...
    沈念sama閱讀 35,735評論 5 346
  • 正文 年R本政府宣布惯殊,位于F島的核電站,受9級特大地震影響也殖,放射性物質(zhì)發(fā)生泄漏土思。R本人自食惡果不足惜,卻給世界環(huán)境...
    茶點故事閱讀 41,354評論 3 330
  • 文/蒙蒙 一忆嗜、第九天 我趴在偏房一處隱蔽的房頂上張望己儒。 院中可真熱鬧,春花似錦捆毫、人聲如沸闪湾。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,936評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽途样。三九已至,卻和暖如春濒憋,著一層夾襖步出監(jiān)牢的瞬間何暇,已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 33,054評論 1 270
  • 我被黑心中介騙來泰國打工凛驮, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留裆站,地道東北人。 一個月前我還...
    沈念sama閱讀 48,224評論 3 371
  • 正文 我出身青樓,卻偏偏與公主長得像宏胯,于是被迫代替她去往敵國和親羽嫡。 傳聞我的和親對象是個殘疾皇子,可洞房花燭夜當(dāng)晚...
    茶點故事閱讀 44,974評論 2 355

推薦閱讀更多精彩內(nèi)容

  • Spring Cloud為開發(fā)人員提供了快速構(gòu)建分布式系統(tǒng)中一些常見模式的工具(例如配置管理肩袍,服務(wù)發(fā)現(xiàn)杭棵,斷路器,智...
    卡卡羅2017閱讀 134,657評論 18 139
  • 生活如水 有靜有動 實則古井不波 其實暗流涌動 酸甜苦辣咸 自己嘗得中 生活如鐘 周而復(fù)始 新舊交替 始終如一 生...
    石頭剪子卟啉閱讀 232評論 0 1
  • 一.Class類的使用 1.在面向?qū)ο蟮氖澜缰辛伺#晔氯f物都是對象2.java語言中靜態(tài)成員和普通數(shù)據(jù)類型不是對象3...
    liangxifeng833閱讀 176評論 0 1
  • 我不知道自己已經(jīng)分手幾天了颜屠,好像還沒有分開,一直都還不能接受我已經(jīng)分手了的事實鹰祸,真的已經(jīng)分手了甫窟,分手后的日...
    苗苗要長大閱讀 182評論 0 0
  • 文/薄涼如夢 水綠總是在想,為什么愛而不得才是最好的蛙婴。這個答案粗井,還是明哲告訴她的。 “水綠街图,下班去逛街嗎...
    薄涼如夢閱讀 505評論 0 3