ActiveResourceKit  v1.2 (498.0)
 All Classes Files Functions Variables Typedefs Enumerator Properties Macros Pages
ARQueuedLoadingURLConnection.m
Go to the documentation of this file.
1 // ActiveResourceKit ARQueuedLoadingURLConnection.m
2 //
3 // Copyright © 2012, Roy Ratcliffe, Pioneering Software, United Kingdom
4 //
5 // Permission is hereby granted, free of charge, to any person obtaining a copy
6 // of this software and associated documentation files (the “Software”), to deal
7 // in the Software without restriction, including without limitation the rights
8 // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 // copies of the Software, and to permit persons to whom the Software is
10 // furnished to do so, subject to the following conditions:
11 //
12 // The above copyright notice and this permission notice shall be included in
13 // all copies or substantial portions of the Software.
14 //
15 // THE SOFTWARE IS PROVIDED “AS IS,” WITHOUT WARRANTY OF ANY KIND, EITHER
16 // EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
17 // MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO
18 // EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES
19 // OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
20 // ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
21 // DEALINGS IN THE SOFTWARE.
22 //
23 //------------------------------------------------------------------------------
24 
26 #import "ARHTTPResponse.h"
27 
28 @implementation ARQueuedLoadingURLConnection
29 
30 - (void)sendRequest:(NSURLRequest *)request completionHandler:(ARConnectionCompletionHandler)completionHandler
31 {
32  // Wrap the response and body together using ARHTTPResponse. Operates// more like Rails, where the response includes the body; but this// involves a subtle semantic shift for Cocoa. Under Cocoa, nil data// indicates an error. This is a subtle change in success-failure// semantics. Cocoa's URL connection interfaces answer non-nil data on// success, nil data on failure. Hence you would typically check for// existence of data to determine success or failure. You can still do// so by asking for the response body. However, you might also check for// non-existing error assuming that nil data and non-nil error// correspond to the same state, namely failure; while non-nil data and// nil error correspond to success.[NSURLConnection sendAsynchronousRequest:request queue:[self operationQueue] completionHandler:^(NSURLResponse *response, NSData *data, NSError *error) {
33 
34 
35 
36 
37 
38 
39 
40 
41 
42 
43 
44  NSParameterAssert((data != nil && error == nil) || (data == nil && error != nil));
45  completionHandler([[ARHTTPResponse alloc] initWithURLResponse:response body:data], error);
46  }];
47 }
48 
49 //------------------------------------------------------------------------------
50 #pragma mark Operation Queue
51 //------------------------------------------------------------------------------
52 
53 @synthesize operationQueue;
54 
55 @end