Re: "Proper" use of SCNetworkReachability?
Re: "Proper" use of SCNetworkReachability?
- Subject: Re: "Proper" use of SCNetworkReachability?
- From: Rick Mann <email@hidden>
- Date: Mon, 08 Jun 2015 16:03:12 -0700
So, the biggest problem has to do with network timeouts. I guess in these situations, SCNR would report connectivity, but it would ultimately fail, resulting in the same behavior, correct? So there should be no problem with going ahead.
> On Jun 8, 2015, at 16:01 , Joshua Graessley <email@hidden> wrote:
>
>
> SCNetworkReachability may return reachable in situations where the connection will not succeed. Your preflight check does not solve the problem.
>
> Sent from my iPhone
>
>> On Jun 8, 2015, at 3:56 PM, Rick Mann <email@hidden> wrote:
>>
>> I thought I'd seen advice from Apple engineers (Quinn?) that instead of first checking SCNetworkReachability, we should just try to make the actual connection, and then take action (e.g. alert the user) only if that fails.
>>
>> But of course, if there's going to be a long timeout, I don't want to make the user wait that long.
>>
>> In my app, there are many moving parts. Background processes try to make network connections (that should not necessarily complain if they fail), sometimes the user initiates network connections...it's challenging to get it all correct.
>>
>> What was the specific advice regarding checking SCNR vs. just trying to connect?
>>
>> Thanks,
>>
>> --
>> Rick Mann
>> email@hidden
>>
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Macnetworkprog mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
--
Rick Mann
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden