According the the doc App Sandbox Design Guide, UNIX Sockets are limited to the 
app or app group in a sandbox environment.

Network Sockets require entitlement for network. 

YMMV

Sent from my iPhone

On Nov 25, 2015, at 5:23 AM, Stéphane Letz <[email protected]> wrote:

>> 
>> 
>> Message: 1
>> Date: Tue, 24 Nov 2015 15:18:57 +0100
>> From: Robert Bielik <[email protected]>
>> To: [email protected]
>> Subject: AudioServerPlugin
>> Message-ID: <[email protected]>
>> Content-Type: text/plain; charset=windows-1252; format=flowed
>> 
>> Hi,
>> 
>> Just setting up to migrate from our KEXT to a AudioServerPlugin, however 
>> due to the sandboxing of the plugin, can someone tell if it is possible to:
>> 1. Communicate with the plugin via a Unix Socket ?
>> 2. Setup a shared memory area between the plugin and a controller 
>> process (for exchanging audio data) ?
>> 
>> TIA
>> /R
> 
> JackRouter (CoreAudio/JACK) bridge still uses the old user-land model. 
> 
> I've done some tests with the newest one 
> (https://developer.apple.com/library/mac/samplecode/AudioDriverExamples/Introduction/Intro.html),
>  but could not (up to now…)  make it work with JACK, although I've have to 
> say I did not spend a lot of time on that…
> 
> Would be interested if you can make your project work, assuming you are ready 
> to share some results or even code.
> 
> Stéphane Letz
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/dangerwillrobinsondanger%40gmail.com
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to