New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate Issues with Reachability Not Restored #408
Comments
I REALLY wish Apple would put together a real reachability framework with a thread-safe objective-c front-end. Until that day, SCReachabilityKit on GitHub works pretty great. There's also Andrew Donoho's more recent revisions to Apple's reachability class. For what it's worth, I went with the former since it fit my project case better. I wrote a layer on top of it that looks primarily at known hosts, suitable for restkit type usage, and for any other unmonitored hosts, it just looks at general network reachability instead of doing another DNS lookup, etc. The kicker is there's only one time where it uses the synchronous getFlags: method, on the initial watch. Everything else is asynchronous, to reduce blocking. I can discuss more if needed, but if you find the SunlightLabs/StatesLege project, look in Classes/Helpers/SLFReachable.m Don't bother trying to build the project though, not all submodules are open to the public yet. G Sent from my iPhone. On Oct 14, 2011, at 1:47 PM, Blake Wattersreply@reply.github.com wrote:
|
Two big things that I'll bring up in the conference call today:
|
…synchronous API's. refs #408 Very large update to the capabilities of the reachability observer as well as (hopefully) fixes for the iOS issues reported on the list.
This restructuring looks good to me. |
…eue suspension on observer mutation instead of baseURL. Cleaned up specs. refs #408 Various header cleanups for RKClient included
… is triggering errors. refs #408
Getting a number of reports about reachability issues not being restored properly.
The text was updated successfully, but these errors were encountered: