Re: Waking up AWDL
Re: Waking up AWDL
- Subject: Re: Waking up AWDL
- From: Neil Alexander <email@hidden>
- Date: Mon, 25 Feb 2019 10:30:57 +0000
- Thread-topic: Waking up AWDL
Understood!
In which case, what is the best way to make an appeal for the AWDL interface to
be scoped for use from within a Network Extension in future versions of
macOS/iOS? That seems like it is the approach that most closely would align
with the public APIs - NetService could be used for browsing and advertising,
wouldn’t need SO_RECV_ANYIF and could them be made to work as a VPN extension
on iOS as well as macOS, instead of relying on setting up utun directly on
macOS and having no such iOS alternative.
Sent from my iPhone
> On 25 Feb 2019, at 10:16, Quinn The Eskimo! <email@hidden> wrote:
>
> That depends on what you mean by “impact”. I suspect you’re asking whether
> App Review will reject your app, and I can’t speak to that. DTS and App
> Review are separate organisations, so I can’t make definitive statements
> about App Review’s policies or procedures.
>
> Speaking from a DTS perspective, we /strongly/ encourage folks to stick to
> public APIs when shipping products to customers (and have done so since long
> before App Review even existed!). Apple works hard to maintain
> release-to-release binary compatibility for public APIs. We offer no such
> guarantees for private stuff. If some core functionality in your product is
> based on private stuff, it could go away without warning and without any
> migration path, and such an event would leave your customers high and dry.
_______________________________________________
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