Last week, I talked about Networking using NSURLConnection. In a future post, I’m going to talk about how to use AFNetworking. But first, I wanted to talk about why you should trust AFNetworking as a project in your project. I haven’t been using github for long. That said, AFNetworking is the best-managed git project I’ve… Continue reading AFNetworking: a well managed open source project
In the past, I’ve talked about Using blocks to remove redundancy. But now I want to explain the pattern I’ve adopted since, which is my favorite block pattern of all. Even though it, too, is all about removing redundancy: handling errors. Although Objective-C supports exceptions, they’re not commonly used. A thrown exception is usually not… Continue reading Using blocks to handle errors
In a previous article, I mentioned how to handle 302/303 redirects to web services. But that’s a fairly advanced topic, and we should have built up to that. What I’m going to cover: The basics of networking using NSURLConnection, part of Apple’s Foundation framework. What I’m not going to cover: How to determine if a… Continue reading Networking using NSURLConnection
So you’re writing your first iPhone app. Welcome! But which version of iOS should you target? This is pretty simple. There’s very little reason not to write for iOS 5.0.
If you’re an application developer: Yes, you should use Automatic Reference Counting (ARC).
If you try to POST to a web API using NSURLConnection that redirects you using a 302 or 303 redirect, you’ll fall over to a GET request. This is intentional, but you can override it.
With Automatic Reference Counting (ARC) coming out soon, you could argue this post is coming almost too late. But there’s a lot of confusion over this, and I don’t think ARC will help much if you don’t understand the why of memory management. After a couple years, I’ve come to adopt some very simple rules… Continue reading Objective-C memory management