On 20 Jan 2016, at 03:05, Michael Norris <michael.nor...@nzsm.ac.nz> wrote:
> So why then is the proximity of 25m good enough for joining ad-hoc Wifi > networks, but not good enough for browsing MPC services over Wifi? Answering that would require an explanation of how the peer-to-peer Wi-Fi protocol works. Alas, that's not possible because it's a) not documented publicly, and b) too complex to permit a short explanation in email. Regardless, from your perspective it doesn't really matter: peer-to-peer Wi-Fi works the way it works and there are no knobs that you can twiddle. The only thing you can do here is file a bug report, but that's not going to yield a solution in the short term. > (As an aside, if I go ahead join the ad-hoc Wifi network I created, the MPC > service suddenly shows up in the client’s service browser… I thought the > point of MPC was that you *didn’t* have to be part of a network for it to > work…?) Right, but that's subject to the limitations of the peer-to-peer network links, which is where we entered this discussion. I think you should try out NSNetService with includesPeerToPeer to see if that helps at all. My guess is that it won't (Multipeer Connectivity is implemented on top of NSNetService, so the peer-to-peer network link limitations tend to apply to both) but it's sufficiently easy to code this up that it's worth testing anyway. Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
