There's been times I had to switch over from one Networking library to another, e.g. from ASIHttpRequest to AFNetworking or even SVHTTPRequest
Sometimes the web side changes API endpoints, and it's a pain if you have to change them all over your app.
You may want to isolate them in one place, so there's no effort needed to make these transitions.
Here's how I prefer to do it.
<!-- more -->
Make a Server class that represents the real server (API endpoint). The base url is defined only on one place, and the other paths are separate constants.
That object also provides a proxy request methods, like GET, POST, PUT, ...
// Server.h#import <Foundation/Foundation.h>staticNSString*constBASE_URI=@"http://supermar.in/api";staticNSString*constNEWS_PATH=@"news";staticNSString*constREVIEWS_PATH=@"reviews";staticNSString*constSOME_STUPID_PATH=@"stupid/path/that_changes.php";@interfaceServer : NSObject+(void)GET:(NSString*)pathparameters:(NSDictionary*)paramscompletion:(void(^)(idJSON,NSError*error))finished;+(void)POST:(NSString*)pathparameters:(NSDictionary*)paramscompletion:(void(^)(idJSON,NSError*error))finished;// this one is here for performing some custom requests, e.g. TWRequest+(void)performRequest:(NSURLRequest*)requestcompletion:(void(^)(idJSON,NSError*error))finished;@end
This is just an stripped down example of implementing a small JSON API. You may want to customize the server responses by your needs.
And the best of all is, if the server switches from JSON to XML or vice versa, the only place to adapt is this class.
Your code should not worry about the server.
Here's how the Server's implementation with AFNetworking looks like:
Let's say you want to completely get rid of AFNetworking and replace it with SVHTTPRequest.
If you had many controllers communicating with the web service, you'd need to change all those files, and adapt the new interfaces.