I do not think so. But more importantly, I donβt think you want it if you can (you can get false positives). Let Rachability complete the course.
If you look at the Reachability demo project, the concept should not call reachabilityWithHostName
and check the currentReachabilityStatus
when you need the Internet. You call currentReachabilityStatus while you delegated your application didFinishLaunchingWithOptions, set up a notification, and Reachability tells you when your Internet connection has changed. I found that subsequent checks on currentReachabilityStatus
very fast (regardless of connection) when I (a) set availability at startup; but (b) check for connectivity in just-in-time mode.
And if you absolutely need to start processing immediately, then the question arises whether you can direct this to the background (for example, dispatch_async()
). For example, my application receives updates from the server, but since this happens in the background, neither I nor my user are aware of the delays.
source share