Added the `response` serialization example back into the README.

README.md

@@ -163,16 +163,17 @@ Alamofire.request(.GET, "http://httpbin.org/get", parameters: ["foo": "bar"])
 
 **Built-in Response Methods**
 
+- `response()`
 - `responseData()`
 - `responseString(encoding: NSStringEncoding)`
 - `responseJSON(options: NSJSONReadingOptions)`
 - `responsePropertyList(options: NSPropertyListReadOptions)`
 
-#### Response Data Handler
+#### Response Handler
 
 ```swift
 Alamofire.request(.GET, "http://httpbin.org/get", parameters: ["foo": "bar"])
-         .responseData { response in
+         .response { request, response, data, error in
              print(request)
              print(response)
              print(data)
@@ -180,6 +181,19 @@ Alamofire.request(.GET, "http://httpbin.org/get", parameters: ["foo": "bar"])
           }
 ```
 
+> The `response` serializer does NOT evaluate any of the response data. It merely forwards on all the information directly from the URL session delegate. We strongly encourage you to leverage the other responser serializers taking advantage of `Response` and `Result` types.
+
+#### Response Data Handler
+
+```swift
+Alamofire.request(.GET, "http://httpbin.org/get", parameters: ["foo": "bar"])
+         .responseData { response in
+             print(response.request)
+             print(response.response)
+             print(response.result)
+          }
+```
+
 #### Response String Handler
 
 ```swift