"Hi Matt, I didn't want to draw to much attention around AFNetworking but was looking for a recent example. But on AFNetworking... We have been pushing towards supporting both concepts in the same code and that both goals can't be obtained with the same code without adding to much bloat. We are grinding away constantly in our team but I've pushed it so that we only actually differ on less than a 300 lines of code (if you ignore that we split out AFXMLDocumentRequestOperation which wasn't necessary but made the code easier to read). We need it to work with AFNetworking in both ways. On one end we have big backend for our sync engine that uses NSOperationQueues and goes right into the NSOperation subclasses all over the place to talk back our web-services (and other magic I can't talk about) and then we have frontend code that simply fires off a few requests using AFHTTPClient to a few third party APIs. We are using one unified stack for both (which helps with testing and logging). We..." - Zac Bowling