• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "Proper" use of SCNetworkReachability?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Proper" use of SCNetworkReachability?


  • Subject: Re: "Proper" use of SCNetworkReachability?
  • From: Vincent Lubet <email@hidden>
  • Date: Mon, 08 Jun 2015 19:02:59 -0700

SCNetworkReachability can only have very limited view of the network topology from the point of view of the device. It should be used as a hint after a connection that something has changed in the configuration of the device and that it is worth trying to connect again.

If the connection failure is not caused by the configuration of the device, then SCNetworkReachability is not going to give a useful hint -- for example when the server or a router is down

Vincent


> On Jun 8, 2015, at 4:03 PM, Rick Mann <email@hidden> wrote:
>
> 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


 _______________________________________________
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


  • Follow-Ups:
    • Re: "Proper" use of SCNetworkReachability?
      • From: David Schinazi <email@hidden>
References: 
 >"Proper" use of SCNetworkReachability? (From: Rick Mann <email@hidden>)
 >Re: "Proper" use of SCNetworkReachability? (From: Joshua Graessley <email@hidden>)
 >Re: "Proper" use of SCNetworkReachability? (From: Rick Mann <email@hidden>)

  • Prev by Date: Re: Re(2): Monitor inbound/outbound network statistics for particular device
  • Next by Date: Re: "Proper" use of SCNetworkReachability?
  • Previous by thread: Re: "Proper" use of SCNetworkReachability?
  • Next by thread: Re: "Proper" use of SCNetworkReachability?
  • Index(es):
    • Date
    • Thread